Facturama integration

Connect Bookkeeping → Integrations → Facturama with your own Facturama API Web username and password. Import fiscal documents, approve a customer collection, review a payment complement, or configure new-invoice rules for confirmed payments. Collection, fiscal issuance, automation and notifications all start disabled.

Connect the issuing account

1. Prepare credentials for the intended production or sandbox API Web account. These are separate environments. See Facturama authentication and environments.
2. Select Connect, enter the environment and credentials, then check the account.
3. Confirm the returned issuing RFC, fiscal name, regime and postal code. One connection represents that issuer in that environment. No MakePay OAuth app registration is required.
4. Leave collection and issuance disabled while reviewing imported documents. When enabling fiscal issuance, select the actual branch, series and payment form from the connected account. Confirm the fiscal settings explicitly.

Credentials are encrypted and are not returned in connection summaries. Replacing credentials for the same issuer and environment preserves original documents and financial history. Sandbox supports inspection and import; real company payments require a production connection for collection or fiscal issuance.

Review documents and approve collection

Import reads supported issued invoices, credit notes and payment receipts, including their available XML evidence. An active CFDI, its original total or its PUE payment method does not establish today's receivable. Review payments, credits and adjustments in your own records, including payments received outside MakePay.

Enable Allow approved invoice payment links. Open an eligible invoice, review its fresh fiscal evidence, enter the exact current receivable and confirm the collection. The approval retains the original issuer, invoice, currency, amount and fiscal evidence for a 12-hour payment link. Share that link with the customer. The connection does not insert it into an existing Facturama PDF or email automatically.

Opening the link checks the approval and original invoice again. Changed fiscal evidence, earlier unresolved payments or an unavailable connection can stop checkout. A confirmed matching MakePay settlement pairs with that original invoice in Bookkeeping; pairing does not itself issue a CFDI in Facturama. Late, conflicting or ambiguous settlements remain attached to their original request for review. Check the original request before preparing another collection.

Issue a reviewed payment complement

Enable Allow approved payment receipts only when ready to issue fiscal documents. Select the actual confirmed MakePay payment or incoming transaction on a connected wallet. Review the receiver's fiscal details, payment and issue dates, currency, valuation, partiality, prior balance, paid amount, remainder and exact tax allocation. Enter and confirm the current receivable separately. A token quantity, including a stablecoin quantity, is not assumed to be a fiat accounting amount.

Review the server preview and explicitly approve the source, valuation, receivable and fiscal facts. The approved operation can then issue a CFDI 4.0 / Payments 2.0 complement through Facturama. Eligible same-currency foreign payments need the required explicit MXN exchange-rate facts. Cross-currency invoice/payment receipt conversion is unsupported. Historical documents can remain readable without being eligible for new fiscal issuance.

Optional automatic receipt for one collection

Enable Allow automatic receipts for approved collections and choose the accounting time zone. For an original unpaid MXN CFDI 4.0 PPD collection, authorize its automatic receipt separately before the customer pays. Review the exact invoice, receiver, amount, next partiality, tax template, branch, series and payment form; then reenter the receivable and confirm all authorizations.

The rule requires you to collect this receivable exclusively through that original link and to confirm that MakePay's first recorded payment confirmation represents the beneficiary receipt time in your accounting process. That recorded instant, converted to your chosen time zone, becomes the payment date. If this policy does not describe your process, use individual receipt review with the actual receipt date.

Only a new matching full confirmation after authorization and within the approved collection window can queue the receipt. An external payment, changed invoice, late confirmation, different amount or incomplete evidence requires individual review. Pause the rule before accepting payment elsewhere or changing the receivable. Pausing a rule or disabling the setting stops new unstarted work; previously dispatched requests retain lookup-only recovery. Saving a rule does not issue a receipt. There is no historical-payment backfill or automatic wallet/foreign-currency receipt conversion.

Create an invoice for an unpaired payment

Enable Allow approved invoices for unpaired payments and choose the native branch, invoice series, issuing time zone and explicit rounding policy. Select an eligible confirmed company payment or incoming connected-wallet transaction. Choose the actual Facturama customer and product by their native identities. Complete missing fiscal metadata in Facturama first.

Review the exact source, fiat valuation, customer, product, quantity, prices, discounts, taxes, payment method/form and fiscal date. Explicitly approve the preview before issuance. The connector does not guess a customer from an email, name or similar amount. A payment already claimed by an invoice or receipt cannot authorize another fiscal operation.

Optional rules for future unmatched payments

Enable Allow automatic invoice rules, then authorize a rule with the customer, product, tax/fiscal template and source scope. Choose one MakePay payment link or an exact connected wallet, chain and asset. MakePay payments retain their confirmed MXN amount. A wallet rule requires your explicit fixed MXN-per-asset valuation; the connector does not supply a market price.

Choose an exact template amount or the supported variable gross amount policy, with explicit limits and currency rounding. Variable rules use one product unit, no discount, and supported percentage or exempt taxes; unsupported tax structures require individual review. Review the sample calculation before authorizing. Only future eligible confirmations within the rule's scope can queue an invoice. Existing payments are not backfilled. Changed native identities, ambiguous rounding, residual values and out-of-policy amounts require review. Pause rules and inspect individual decisions in the invoice panel.

Notifications, sync and recovery

Optional in-app notifications cover matched collections, issued invoices/receipts and review or sync problems. They start disabled and are deduplicated. Facturama's own independently configured automations still apply.

Imports continue in bounded batches through Sync and the scheduled worker. The manager paginates stored documents, collections and operation history. Financial approval rereads relevant native evidence; an import finishing does not by itself authorize collection or issuance. Complete fresh observations are bounded to 10,000 documents and by byte/time limits. Unsupported formats, conflicting evidence or incomplete coverage remain in review.

Before dispatch, MakePay retains an immutable approved request, source, actor, reference and fiscal dates. It verifies the resulting native document and XML against that request. If the response is uncertain, it searches the original reference and never automatically posts a replacement. Keep the original operation and displayed reference when reviewing a delayed result. Only an approval that has never started can be withdrawn and reviewed again. Disconnecting pauses new work and preserves history; review existing settlements and fiscal operations first.

Supported scope

Current issuance uses CFDI 4.0 invoices and Payments 2.0 receipts. Supported historical CFDI 3.3 / Payments 1.0 documents can inform review. Unsupported fiscal structures remain in review. Fiscal history is not an independent accounts-receivable ledger and cannot prove the absence of external payments.

Facturama API Web does not establish a generic wallet-expense ledger or supporting expense-file upload workflow for this connection. A type E credit note is not an expense export. Refunds, cancellations, corrections and document-email delivery require separate handling. The connector's document comparisons are not SAT certification, full XML-schema or digital-signature validation, or independent approval of your tax treatment.

See creating API Web CFDIs, querying issued documents and Facturama's recovery guidance.