Integrate your product with ChatFin agents
For companies that build software, not for firms that deliver it to clients. Your product supplies data the agents read, consumes what they prepare, or embeds the question itself.
Companies that build software
Four product types come to us most often. If you sell implementation services rather than a product, the solutions partner track fits better.
Finance applications
Capture, expense, close management, lease and contract tools that already hold documents or schedules the agents need to read.
Banking and payment platforms
Statement lines, remittances and payment references, delivered as structured data rather than an attachment somebody opens.
Analytics and vertical products
Reporting tools, and vertical software carrying job, project or field data that finance needs and the ERP does not hold.
Three directions, one system of record
ChatFin reads from and writes to the ERP through that system's published interfaces, with a named person approving every posting. Your product joins on one of three sides.
Where your product joins
The ERP stays the system of record in all three directions. ChatFin is not a second ledger, and neither is your product.
- Supply data the agents read
- Consume prepared output such as exception queues
- Embed the question, so your users get an answer from live ERP data
- Which ERP your customers run shapes the work more than your side does
Security, permissions and the approval boundary
One rule shapes every ChatFin integration. Nothing posts without a named approver, including where your product runs an approval step of its own.
- Credentials stay separate, and your product keeps its own
- The ERP connection uses the customer's service account
- Scope is set by their IT owner in writing
- The request, the rows read, the payload and the approver are logged and exportable
- Its own credentials
- Its own approval steps, where you have them
- What your users see while an approval is pending
- The customer's scoped service account
- The prepared entry and its evidence
- A named approver on every posting
Cash application, with the remittance you hold
A customer pays 312,480.00 against forty invoices, three of them short paid for freight, and the remittance carries purchase order numbers rather than invoice numbers.
Thirty seven lines apply untouched
The three needing judgement arrive already isolated, with a deduction reason proposed for each.
- Your product contributes the remittance and payment reference as structured lines
- The agent matches on amount, purchase order and customer history
- The analyst approves the application and the deductions, or corrects one
- The decision and the evidence are recorded in ChatFin and visible in your product
ERP coverage across joint customers
Before a scoping call
Where your data duplicates what the ERP already holds, a connection adds maintenance and little else. We would rather say that early.
What is the ChatFin technology partner program?
It is the track for software companies that want their product to work with ChatFin rather than resell it. Typical partners build finance applications, banking and payment platforms, analytics tools, or vertical products carrying job and project data. The integration runs in one of three directions. Your product supplies data the agents read, it consumes prepared output such as exception queues, or it embeds the question so your users get an answer from live ERP data.
How much engineering effort does the integration take?
It depends on how many objects cross the boundary and whether your product already exposes them through an API. One direction, three or four objects, clear field ownership and a defined failure path is a small piece of work. Effort grows when the same value is owned on both sides, when data arrives only as an attachment, or when the customer's ERP has no governed write interface. A scoping session settles those before anyone estimates.
Who holds the credentials and who approves a posting?
Credentials stay separate. Your product keeps its own, and the ERP connection uses the customer's service account, scoped by their IT owner in writing. Postings are never silent. A ChatFin agent prepares the entry and a named person approves it through a governed ERP interface, even where your product has an approval step of its own. The request, the rows read, the payload and the approver are logged and exportable.
Send the use case and we will scope it
Tell us what your product holds, which ERP your customers run and which direction the data moves. We will come back with the shape of the integration.
Bring one use case and the objects behind it
Ask what a joint customer's security questionnaire looks like
We will say where the integration is thin