Integrations

Our native integrations detect when you issue an invoice in your ERP or close a sale in your point of sale, and handle the rest: mapping to the e-CF format, XMLDSig signing, submission to the DGII, and returning the eNCF/QR to your system.

Connect with what you already use

Native integrations with the most common ERPs and point-of-sale systems in DR. If yours isn’t listed, we connect via API.

Loyverse

Point of sale · OAuth

In review

Cloud point of sale. We listen to the receipts webhook: every closed sale becomes an e-CF — a tax credit invoice when the customer has a tax ID, a consumer invoice when not — and refunds become credit notes. The invoice reaches the customer by email, and the merchant can print it from our portal. Read-only in Loyverse: we never change anything in the merchant’s account.

Invoice Ninja

Self-hosted / Cloud

Available

Connect your Invoice Ninja instance. Each invoice you issue is signed with XMLDSig and sent to the DGII automatically. The eNCF, security code, and QR are written back to your invoice as custom fields.

QuickBooks Online

Cloud · OAuth

Available

Intuit Webhook + OAuth. We detect new Invoices, map them to the e-CF format, sign and submit. No polling, no local agent — fully cloud.

QuickBooks Desktop

On-premise · QBWC

Available

QBWC connector installable on Windows. Two-way sync with your .QBW file. Ideal for companies on legacy QuickBooks Desktop.

Your ERP

REST · X-API-Key

Via API

Using SAP, Odoo, ERPNext, Microsip, or a custom system? Our REST API accepts the eNCF generated by your system or assigns it automatically. Public documentation.

How does an integration work?

  1. 1
    Connect your account. From the Ment portal, authorize access (OAuth for Loyverse and QBO, API key for Invoice Ninja, QBWC connector for QBD). Zero code.
  2. 2
    Configure the mapping. Define which ERP field maps to the e-CF type, which customer represents each tipoIngreso, and where the returned eNCF is stored. The default mapping covers 90% of cases.
  3. 3
    Automatic issuance. Each new invoice in your ERP triggers: mapping to e-CF, XMLDSig signing, submission to the DGII, status polling. The eNCF, security code, and QR are written back to your original invoice.
  4. 4
    Full visibility. From the portal you see every issued e-CF, its DGII status, and download the signed PDF/XML in one click. Cancellations and credit/debit notes are managed there too.

Your ERP isn’t listed?

Most ERPs connect via our REST API in a few hours. Let’s talk.