Invoice & receivable exports
Premium invoices, program references and open balances from existing systems.
Agree first: Authorized files, stable identifiers and agreed gross/net meaning.
Proposed reconciliation pathways
The first proposed Grenvo workflow uses authorized exports for one specialty program and cycle. Agree source meaning, matching rules and accounting acceptance before choosing an API or automated connection.
No live connector, certification or vendor partnership is claimed. Every pathway depends on your installed system, access rights and validation with its owner.
Premium invoices, program references and open balances from existing systems.
Agree first: Authorized files, stable identifiers and agreed gross/net meaning.
Source rows showing amounts, fees, references and available receipt evidence.
Agree first: Source rights, completeness, overlap and original row identity.
Reviewed allocation and fee treatment, with assigned unresolved differences.
Agree first: Rule owner, approval, currency, rounding and correction handling.
Totals, allocations, fee lines, source references and open items for existing tools.
Agree first: Named approver, accepted format and evidence of acceptance or rejection.
These guides explore premium and accounting records in selected systems. They are discovery candidates, not a universal shortlist or working integrations. Your actual exports determine the first mapping.
Agree program, cycle, currency, source owners and stable row identifiers.
Confirm partial and split allocations, fee treatment, duplicate rows and corrections with finance.
Define the package and existing-tool evidence that establishes accounting acceptance.
APIs, broader application-to-coverage coordination, claims and payment rails need their own validated scope. They are not prerequisites to file reconciliation.
Discuss one program, the files your team uses and the accounting package it needs to accept.