Skip to content

Financing flow

Financing is decided per invoice, never per batch. Send twenty invoices in one call and you can get twenty different answers — that is normal, not an error. The invoices that are not financed still matter: they are the collateral the limit is set against.

What one invoice passes through

Every receivable the client sends runs this sequence. Noja runs it; the client asks for nothing. Any stage can end it, and the stages after that never run.

Payables, and the occasional receivable withheld with financingIntent: exclude, skip the pipeline entirely and go straight into the book. They are not assessed, not scored, and not rejected — they are collateral.

AUTOMATED TRIAGEHUMAN REVIEWPOST /invoicesConsent + client checkInvoice eligibilityPolicy criteriaDebtor assessmentAvailable limitAnalyst reviewFour-eyes approvalreceivable, not withhelddue date not yet passedLayer 1 ruleshuman decisionmanager sign-offFinancedadvance paid to client403 consent_requiredpast due datehard rule fireddebtor rating below thresholdlimit exceededanalyst rejectsmanager rejectswhole request refused, nothing storedterminal — never becomes eligiblefinancing_blocked = truethis invoice onlyheadroom smaller than the advancefinancing_rejectedfinancing_rejected
One invoice, nine stages. Noja runs all nine; the client requests nothing. Eligibility closes at the due date, which is why invoices should arrive as they are issued. Only the first exit is request-level — every other rejection affects that invoice alone, which is why a single batch returns mixed outcomes.

The consent gate is the only one that rejects your whole request. Everything below it is evaluated per invoice.

The eligibility stage is worth dwelling on, because it is the one that surprises people: an invoice past its due date can never be financed. Financing is an advance against a receivable the debtor has not yet had to pay. Once the due date passes, the invoice is a collection matter, and no later event makes it eligible again.

Why one batch returns several answers

Two stages reject invoices individually, and they are the two that cause almost all partial approvals:

  • Debtor assessment — the invoice is fine, but its debtor is not. A weak credit rating, a debtor in collections, or a debtor Noja has no data on. Nothing about the client changes; the next invoice to a different debtor can still be approved.
  • Available limit — invoices are assessed in the order received and each approval consumes headroom. Once the remaining headroom is smaller than the next advance, the rest are rejected even though they are otherwise perfectly financeable.

That ordering matters: a batch is not evaluated as a pool and does not get part-funded pro rata. Each invoice either fits in what is left, or it does not.

An invoice carrying its own requestedAdvanceRate draws proportionally more or less headroom than the facility rate would, so a single raised rate early in a batch can be the reason a later invoice no longer fits.

POST /invoices/batch5 invoices · €27,442.50 · facility advance rate 80%limit €25,000 · used €6,600available headroom €18,400INVOICEAMOUNTADVANCE 80%OUTCOME2026-04172026-04182026-04192026-04202026-0421€4,242.50€7,800.00€3,100.00€6,900.00€5,400.00€3,394.00€6,240.00—€5,520.00—fits remaining headroomfits remaining headroomdebtor credit rating below thresholdfits remaining headroomneeds €4,320 · €3,246 headroom leftfinancing_approvedfinancing_approvedfinancing_rejectedfinancing_approvedfinancing_rejectedHEADROOM CONSUMED, IN THE ORDER RECEIVED041704180420€3,246 left€18,400 limit0421 needs €4,320 — overshoots the limit, so it is rejected outright
Five invoices, one call, three outcomes. Each advance here is the facility's 80%. Approvals consume headroom in the order received; the last invoice is rejected because what remains is smaller than its advance, not because anything is wrong with it.

Note what did not happen to invoice 2026-0421: it was not part-funded for the €3,246 that remained. Advances are all-or-nothing per invoice.

Rejection reasons

Reason Scope Retry?
Consent not recorded Whole request Yes, once the client consents or signs
Past due date One invoice Never
Hard policy rule fired One invoice No, until the underlying fact changes
Debtor credit rating One invoice No for this debtor; other debtors unaffected
Debtor unknown or unverifiable One invoice Yes, after sending the debtor's registration number
Limit exceeded One invoice Only while the due date has not passed
Invoice already settled or credited One invoice No
Analyst or manager rejection One invoice No

Only limit exceeded is genuinely temporary, and even that has a deadline. As financed invoices settle, headroom returns and a rejected invoice can be resubmitted with PATCH /invoices/{invoiceId} — but only if its due date is still ahead. An invoice rejected for limit late in its term may simply run out of time, and that is the expected behaviour, not an edge case to engineer around.

In every case the invoice stays in the book. A financing rejection removes the advance, never the collateral.

What you receive

A batch call returns immediately with a job id — decisions arrive later, one webhook per invoice:

{
  "eventId": "evt_0193f34a2c917e55",
  "type": "invoice.financing_decision",
  "occurredAt": "2026-09-14T10:02:47Z",
  "data": {
    "invoiceNumber": "2026-0421",
    "client": { "countryCode": "NL", "registrationNumber": "68123456" },
    "financingState": "financing_rejected",
    "reason": "limit_exceeded",
    "amountRequested": { "amount": 432000, "currency": "EUR" },
    "availableHeadroom": { "amount": 324600, "currency": "EUR" }
  }
}

Do not wait for the batch to finish

There is no "batch decided" event, because there is no batch-level decision. Handle each invoice.financing_decision as it arrives and reconcile at the end with GET /invoices filtered on financingState — treating the batch as one unit is the most common integration mistake here.

Showing this to a user

Partial approval reads as failure unless you frame it. Three things worth surfacing:

  1. The total actually advanced, not the count of approvals. "€15,154 on its way" is the useful number.
  2. Why each rejection happened, separated into "nothing you can do" (debtor rating, past due date) and "try again while there is still time" (limit exceeded). They call for different user actions, and the second has a deadline worth showing.
  3. Remaining headroom, from credit conditions — it tells the user what a second submission could achieve.