Practical guides for B2B finance teams.
No fluff. The frameworks, benchmarks and definitions we share with finance leaders evaluating autonomous AR. Many before they even talk to us.
Best AR automation software for B2B collections in 2026
Three key takeaways, nine product reviews and practical advice on choosing software that works with your finance team and existing systems.
Read the article →Free tool · no sign-upDSO calculator: how much of your DSO is actually fixable?
Work out your DSO and your Best Possible DSO, then see the gap between them: the days your payment terms do not explain, what that ties up in cash, and what it costs you a year to carry.
Open the DSO calculator →In-depth reading.
Best AR automation software for B2B collections in 2026
Three key takeaways, nine product reviews and practical advice on choosing software that works with your finance team and existing systems.
Read: Best AR automation software for B2B collections in 2026 →What is autonomous accounts receivable?
A plain-language definition of autonomous AR (the category Finero pioneered) and how it differs from AR automation, dunning tools and collection agencies.
Read: What is autonomous accounts receivable? →How to reduce days sales outstanding (DSO) without hiring
Five operational changes. Chase cadence, hosted payments, ERP-level reconciliation, dispute SLAs and self-serve portals. That compound into double-digit DSO improvement.
Read: How to reduce days sales outstanding (DSO) without hiring →Choosing a B2B payment provider in 2026
A buyer's framework: acquiring footprint, B2B-specific features (ACH, surcharging, tokens), fees, settlement timing, and what to negotiate.
Read: Choosing a B2B payment provider in 2026 →Dynamics 365 Finance AR automation
What collections process automation, Copilot and payment predictions do natively in Dynamics 365 Finance, where they stop, and when to add an AR platform.
Read: Dynamics 365 Finance AR automation →MCP server for accounts receivable
Connect an assistant to live AR data over the Model Context Protocol. Mostly reads plus narrow writes, OAuth 2.1, and the session acts as the person who approved it.
Read: MCP server for accounts receivable →B2B invoicing and collection
Why most late payments start at invoicing: the seven invoicing mistakes that delay payment, and the escalation ladder for invoices that stall.
Read: B2B invoicing and collection →Oracle Fusion 26B receivables
Every 26B write-up was a spring preview aimed at payables. What the release actually changed for receivables, what you cannot switch on, and what Advanced Collections got.
Read: Oracle Fusion 26B receivables →B2B payment collection: a practical guide
The five-stage invoice collection lifecycle, the metrics that expose a broken process, and the three operating models finance teams choose between.
Read: B2B payment collection: a practical guide →Oracle Fusion 26C cash application
Oracle 26C makes receipt application deterministic. What applyReceipt changes, why matching allocated by rule before it, and what that means for unapplied cash.
Read: Oracle Fusion 26C cash application →B2B payment reminder email templates
Seven copy-paste reminder emails (from pre-due nudge to final demand) mapped to the chase cadence that actually gets B2B invoices paid.
Read: B2B payment reminder email templates →Cash application: the invisible AR bottleneck
Why unapplied cash makes your aging report lie, what manual matching really costs, and how line-level automated cash application posts back to the ERP.
Read: Cash application: the invisible AR bottleneck →Accounts receivable automation: what it does, where it stops
What AR automation covers, what it costs, a seven-point evaluation checklist, and the question that decides whether automation is enough or you need autonomy.
Read: Accounts receivable automation: what it does, where it stops →Receivables terminology, defined.
If you're new to AR or briefing a stakeholder, these are the terms that come up most often around Finero.
- Accounts receivable (AR)
- Accounts receivable (AR) is the outstanding invoices a business is owed by customers, typically tracked as an asset on the balance sheet.
- DSO (days sales outstanding)
- DSO (days sales outstanding) is the average number of days it takes a business to collect cash after a sale. Lower is better.
- Cash application
- Cash application is the process of matching incoming payments to the correct customer invoices and posting them in the ledger.
- Dunning
- Dunning is the structured sequence of reminders a business sends to collect an overdue invoice, escalating in tone and channel as the debt ages.
- Tokenisation
- Tokenisation replaces sensitive payment details, such as a card number, with a meaningless substitute value called a token, which can be stored and reused without exposing the original data.
- Lockbox
- A lockbox is a bank-operated postal address where customer payments are sent, opened, deposited and reported by the bank on the business's behalf.
- ACH / Bacs / SEPA
- ACH, Bacs and SEPA are the domestic bank transfer schemes of the United States, the United Kingdom and the euro area: batch-based rails used to move money between bank accounts at far lower cost than cards.
- Open item
- Open-item accounting tracks each invoice individually until it is settled, rather than tracking only a running customer balance.
- Promise to pay (PTP)
- A promise to pay (PTP) is a commitment from a customer to settle a specific invoice or balance by a stated date, recorded so it can be tracked and followed up.
- Unapplied cash
- Unapplied cash is money a business has received but has not yet matched to specific customer invoices, so it sits in the ledger without reducing any receivable.
- Collections Effectiveness Index (CEI)
- The Collections Effectiveness Index (CEI) is a percentage measuring how much of the receivables available to collect in a period a business actually collected. 100% means everything collectable was collected.
API and developer documentation.
Finero has a public REST API for external systems and AI agents. It is documented in the application, not here. Those docs are generated from the API itself and are always current.
Machine-readable entry point
Start here if you are an agent. Authentication, available operations, identifiers, pagination, limits, errors, and task recipes.
app.getfinero.com/llms.txt →API reference
Full endpoint and schema documentation, with field-level descriptions.
app.getfinero.com/api-docs →OpenAPI specification
Machine-readable specification. Generate a client directly from this.
api.getfinero.com/…/openapi.json →Which source is authoritative
- This marketing site describes Finero, its value, use cases, and product direction.
- The application documentation describes what the API supports today.
- If the two ever disagree, the application documentation is correct.
Looking for something specific?
We're publishing depth on each ERP, each payment provider and each industry vertical. Until then, our team is happy to share what we've seen in the wild.
See autonomous AR invoice collection in action
Book a 30-minute demo with a Finero expert. See how Finero chases, collects, and reconciles invoices end-to-end.