Skip to content
_ACCOUNTS RECEIVABLE/

Cash application that applies itself

Invoices, lockbox and card payments, discounts, and write-offs: an AR system of record where every payment lands on the right invoice, in the right entity, in the right currency.

invoice
payment
application
residual
_THE PROBLEM/

Your team touches every payment twice

Cash application at enterprise scale is rekeying, not accounting.

Payments arrive through lockboxes and card processors, invoices live in the ERP, and matching them is manual: short-pays, early-pay discounts, and cross-currency payments all land unapplied and wait for a human.

01

Card and lockbox payments are double-touched and rekeyed before they apply.

02

A USD payment against a CAD balance sits unapplied until someone does FX by hand.

03

Small-balance write-offs and early-pay discounts are policies in someone's head, not rules in the system.

04

Every correction and adjustment must be traceable for SOX, and reconstructing them is archaeology.

_PROOF/ A North American environmental services leader runs its AR system of record on Formance, from invoice to applied cash.

_FLOW OF FUNDS/

From invoice to applied cash

Billed, collected, applied, and cleared: one double-entry chain.

An invoice opens the receivable, the payment arrives through a lockbox or processor, application matches it to the invoice (discounts and tolerable short-pays posting as explicit rules), and the residual clears by policy, not by hand.

applied vs unapplied
invoicereceivable opened
paymentlockbox · card
applicationmatched to invoice
residualdiscount · write-off
_CAPABILITIES/

The primitives AR teams need

Built on the open-source Formance ledger.

Event-driven receivables, rule-based application, and native multi-currency, composed for enterprise order-to-cash.

_RECEIVABLES LEDGER/

Invoices, payments, and adjustments posted as double-entry events from your OMS and ERP; balances derived per customer, invoice, entity, and cost center.

roll-up any dimension

_CASH APPLICATION/

Lockbox and processor receipts matched to open invoices by rule: exact, partial, and short-pay scenarios post deterministically, no rekeying.

no double-touch

Read the Numscript docs
_DISCOUNTS & WRITE-OFFS/

Early-pay discounts and small-balance tolerances declared as Numscript policies: applied consistently, approved by role, auditable forever.

policy, not habit

_NATIVE MULTI-CURRENCY/

CAD and USD (or any pair) held natively per account; cross-currency application posts with an explicit conversion, never a mental FX step.

explicit FX legs

_BY THE NUMBERS/

Order-to-cash, by design

rekeyed payments0rule-based application
roll-up dimensionanycustomer · entity · cost center
multi-currency ARnativeCAD · USD · any pair
correction traceability100%SOX-ready · immutable
_NUMSCRIPT/

Application is a rule, not a task

Payment applied, discount honored, residual written off: one transaction.

One Numscript transaction applies the lockbox payment to the invoice, honors the early-pay discount, and clears the residual within tolerance, every leg explicit and auditable.

apply.num
// Apply a lockbox payment with early-pay discount
vars {
  account $invoice
  monetary $payment
  monetary $discount
}

send $payment (
  source = @counterparty:lockbox
  destination = $invoice
)

// Early-pay discount clears the remainder
send $discount (
  source = @platform:discounts:early-pay
  destination = $invoice
)
_VOICES/

Trusted by builders

LiberisLiberis
Formance enabled us to ship new lending products faster by providing a customizable foundation that let us reliably express the complexities of our flow of funds.

Embedded finance · reconciliation across 14 countries

See customer story
DoctolibDoctolib
Formance is the foundation of our Financial OS, the open-source approach lets us retain control over this key component.

Healthcare · Financial OS

PayflipPayflip
Formance helped us kick off our move into fintech, with robust infrastructure and intuitive developer tooling.

Benefits · fintech infrastructure

_TRUST/

Built for regulated money.

Enterprise controls, the certifications auditors ask for, and an immutable record, out of the box.

See our trust center
THE COMPLIANCE STACK
IAM, RBAC & SSO
Non-repudiation
Audit logs
Observability & monitoring
Real-time events
Admin console
_AUDIT-LOG/ NON-REPUDIATION

09:41:07Z AUDIT gateway POST /api/ledger/v2/main/transactions 200 sub:ops@acme.io

09:41:09Z LOG id:4093 NEW_TRANSACTION ledger:main

09:41:12Z LOG id:4094 SET_METADATA ledger:main

09:41:15Z LOG id:4095 REVERTED_TRANSACTION ledger:main

09:41:18Z AUDIT gateway GET /api/ledger/v2/main/logs 200 sub:audit@acme.io

CERTIFICATIONS
AICPA SOC IICERTIFIED
ISO 27001CERTIFIED
DORACOMPLIANT
REGULATORY FRAMEWORKS
EMIFCAMTLNYDFS Trust CharterOCC CharterMiCAGENIUS
_ATTESTED/
FAQ

Enterprise AR, answered

01 / DOES FORMANCE CREATE THE INVOICES?

No: it is the AR system of record, not the billing application. Your OMS and billing systems emit events; the ledger records them in double-entry and derives every balance.

02 / HOW DO SHORT-PAYS AND TOLERANCES WORK?

Tolerances and dealer terms are declared rules: a payment within tolerance applies and the residual writes off automatically, with the policy and the posting both auditable.

03 / WHAT ABOUT CROSS-CURRENCY PAYMENTS?

A USD payment against a CAD invoice posts with an explicit conversion leg at a booked rate: applied immediately, no unapplied queue, both currencies exact.

04 / IS IT SOX-AUDITABLE?

Yes: every posting, correction, and write-off is immutable and hash-linked, with role-based approval upstream, so the audit trail is the record itself.

_GET STARTED/

Close the books without touching the payments

See how Formance fits your order-to-cash: book a demo or start building.