Xero, ready to run.
The Xero integration brings your ledger into a case. Floowed pulls the contact, the bills and the payment history, checks them against your rules, and writes the outcome back into Xero: the cleared supplier into a contact group, the decision into the contact's history.
What it does.
What Floowed reads from Xero
- Contacts, including supplier and customer records
- Invoices, bills and credit notes
- Bank transactions and payment history
- Aged receivables and payables, per contact
What it writes back
- The outcome as a contact group, which the rest of your stack can filter on
- A credit note or an invoice, where the decision creates one
- A note recording the decision in the contact's history
- The supporting file, attached to the contact or the invoice
One thing worth being straight about: Xero has a credit limit in its own interface, but its API does not expose that field, so nothing can set it for you. Your rules set the limit and Floowed records it where the API can reach, and the limit itself is applied wherever you enforce it.
A supplier onboarding case, from request to approved contact in Xero.
- Gather
A new supplier request arrives in the accounts payable mailbox in Outlook. Floowed opens a case and checks Xero for an existing contact with the same name or tax number.
- Interpret
Floowed reads the documents the supplier sent, scanned or native: the bank letter, the tax registration and the signed terms, and compares them with the request.
- Chase
A missing bank letter goes back to the supplier by email. The budget holder is asked in Slack or the Floowed Dashboard to confirm the spend.
- Decide
Your onboarding rules run in the deterministic policy engine. A supplier that does not fit them goes to the finance lead to decide.
- Act
Floowed creates the contact in Xero, adds it to your approved suppliers group, attaches the documents, writes the decision to the contact's history and files the evidence in Google Drive.
Used in the same case
The connection, in detail.
How it connects.
- 1
Connect Xero
Using OAuth 2.0 authorization code flow, with offline_access for a lasting connection. Each connected organization is its own tenant. Nothing migrates and nothing is replaced.
- 2
Build your operation
Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.
- 3
Let it run
Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.
Questions
Does Floowed integrate with Xero?
Yes. The Xero integration connects over OAuth 2.0 across contacts, invoices, bills, credit notes, payments and bank transactions.
How does the Xero integration connect?
Through Xero's OAuth 2.0 sign-in against your organization, with the scopes you approve. Several organizations can be connected; each is a separate tenant with its own rules.
What can Floowed do with Xero data?
It reads payment behavior and exposure out of the ledger, including the aged receivables and payables per contact, and combines that with whatever else the case needs. The outcome goes back as a contact group, a history note, an attachment, or a credit note where one is warranted.
Do I need to build anything to use it?
No. Describe the operation in the Floowed Dashboard, Slack or Microsoft Teams, connect Xero, and set your rules and the point at which a person still decides.
Is my Xero data secure?
Access is limited to the scopes you approve and can be revoked from Xero at any time. Every case keeps a full record: what was read, who was asked, which rule decided it and what was written where.
What does the Xero integration cost?
Nothing extra. Integrations are included, and you pay for the work Floowed does on a case. Start free with $80 of credits, no card and no sales call.
Start with Xero. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.