--- title: "GetMyInvoices Integration" description: "GetMyInvoices collects invoices and receipts automatically from supplier portals, email inboxes, and bank transactions. Agents pull the documents it has captured, read their extracted data, tag transactions, and hand the files to the next system in the flow." url: https://flowrunner.ai/integrations/getmyinvoices date_modified: 2026-09-04T14:53:04-07:00 --- # GetMyInvoices [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) GetMyInvoices collects invoices and receipts automatically from supplier portals, email inboxes, and bank transactions. Agents pull the documents it has captured, read their extracted data, tag transactions, and hand the files to the next system in the flow. 39 actions · API key · available [GetMyInvoices website](https://www.getmyinvoices.com/) · [Platform Documentation](https://api.getmyinvoices.com/accounts/v3/doc/) · Capability data verified 2026-08-24 1. A scheduled sweep runs against everything changed since the last run 2. List Documents returns newly captured invoices with their supplier and amount metadata 3. The agent reads which documents still carry no assigned bank transaction 4. Assign Document To Transaction pairs the matches it can evidence 5. The agent confirms each supplier record carries the creditor number an export depends on 6. The AP owner receives the transactions left unmatched, with candidate documents attached 7. The AP owner decides which transactions will never have an invoice and can be cleared ## What This Integration Enables GetMyInvoices is not accounting software and it does not issue anything. It is the step before the books: it signs in to supplier portals, reads email inboxes, imports bank transactions, and files what it collects as documents with metadata attached, ready to be pushed on to whatever system keeps the ledger. Build flows around that shape and the connector is a strong fit. Ask it to produce an invoice for a customer and you have picked the wrong tool. FlowRunner agents work the capture and reconciliation cycle. They read documents changed since a timestamp, upload files with optical reading switched on so a bare upload returns a supplier, number, dates, and amounts, check whether a file is already held before uploading it, maintain the company records that documents are filed against, and pair documents to bank transactions. The API has two behaviors worth designing around. A successful HTTP status can still carry a failure in the body, and the connector reads the body and raises so a refused call cannot look like an empty result. And the pair of List Documents with a changed-since filter and List Deleted Documents with a deleted-since filter keeps a mirror exactly in step without re-reading the account. There is no webhook registration here, so flows are scheduled around those filters rather than pretending to listen. The judgment worth reserving belongs to the reconciliation queue and to the collection itself, which is where FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) design puts it. ### Without FlowRunner **Invoices chased across portals**: Someone signs in to each supplier portal every month to download what is owed **The same invoice filed twice**: A forwarded mail attachment gets uploaded again on every reprocessing run **Reconciliation is a spreadsheet**: Bank lines and documents are matched by eye in an export that goes stale immediately ### With FlowRunner **Collection runs on its own**: Portals, inboxes, and bank feeds deliver into one place and a flow reads what arrived **Duplicates caught before upload**: Each file is checked against what the account already holds before anything is filed **Reconciliation is a work list**: Unmatched documents and unmatched transactions are surfaced as two queues that shrink ## Use Case Scenarios ### A mirror that stays honest An accounting system needs everything GetMyInvoices captured, and the usual approach re-reads the account and hopes. The sync pair does better. List Documents with a changed-since timestamp returns everything created or changed, List Deleted Documents with a deleted-since timestamp returns everything that disappeared, and storing the run timestamp makes the next run exact. The agent pushes new and changed documents into [Xero](https://flowrunner.ai/integrations/xero) or [QuickBooks Online](https://flowrunner.ai/integrations/quickbooks-online) and retires the deleted ones rather than leaving orphans behind. Line items are left switched off for wide date ranges, because they make the response much larger for data most flows do not use. The creditor number gets checked on the way through, since it is the field that decides whether an export lands in the right supplier account and it is the easiest one to leave empty. ### Forwarded mail filed once Suppliers email invoices to a shared mailbox, and a mailbox gets reprocessed. The agent reads each attachment from [Gmail](https://flowrunner.ai/integrations/gmail-service) and calls Check Document Exists first, which takes the file and reports whether the account already holds it. That single call is the difference between filing an invoice once and filing it again every time the mailbox is swept, and it is cheaper than uploading and cleaning up afterwards. For genuinely new files, Upload Document with optical reading switched on lets GetMyInvoices pull the supplier, number, dates, and amounts off the file, so a bare upload is often the whole job. The file travels as encoded data inside the request rather than as a form upload, and Update Document changes metadata only, because the stored file itself cannot be replaced. ### Two queues instead of one spreadsheet Reconciliation here is a loop the product was designed for, and it works best when the agent keeps the two sides separate. List Documents filtered to those with no assigned transaction is the document side. List Transactions for the named bank accounts is the money side, and it requires at least one account to be named because there is no read across everything. The agent matches on amount, date, and supplier, calls Assign Document To Transaction where the evidence is clear, and tags the rest. A negative transaction amount is money going out, since the sign is the direction and there is no separate field, so the agent reads it rather than assuming. What is left is posted to the AP owner in [Slack](https://flowrunner.ai/integrations/slack): the unmatched transactions, the closest documents, and a note on which look like transfers or salaries that will never have an invoice at all. ## Human-in-Loop Highlight Delete Portal Connection is the operation on this connector that fails silently by design. It stops collection from that supplier portal, and everything already filed stays exactly where it is, so nothing looks broken. The account keeps working. Documents simply stop arriving from one supplier, and the first evidence is usually a month-end close where a recurring cost is missing and nobody can say when it stopped. Recovery is not automatic either, because reconnecting a portal means credentials a person holds rather than an API call, which is what Request Reconnect exists to ask for. That is why the cleanup agent that prunes stale portal connections stops before it prunes. It posts: "Portal connection Deutsche Telekom Business has returned an authentication failure on the last four sweeps. It captured 11 documents in the previous 90 days, most recently 14 days ago. Deleting the connection stops collection and needs a person to reconnect it. Delete, or request a reconnect?" The AP owner answers. Ignoring a transaction is a different matter and runs unattended, because turning it back on puts the transaction straight back on the queue. The gate belongs where the undo does not exist. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 39 actions ### Account 4 - **Check API Status** Confirms the API is reachable and the key is accepted. The cheap first step in a scheduled flow. - **Get Account Details** Reads the account's own details and configuration. - **List Users** Lists the users on the account. Used to resolve who a decision should be routed to. - **List Sync Accounts** Lists the connected sources documents arrive from. ### Documents 11 - **List Documents** Lists captured documents, with a changed-since filter for incremental reads and a filter for those with no assigned bank transaction. Line items are off by default and are worth leaving off for wide date ranges. - **Get Document** Retrieves one document with its metadata, optionally including the file itself encoded inside the response. - **Upload Document** Files a new document. With optical reading switched on, GetMyInvoices reads the supplier, number, dates, and amounts off the file. - **Update Document** Changes a document's metadata. The stored file cannot be replaced, only its description. - **Delete Document** Removes a document from the account. - **List Deleted Documents** Lists documents deleted since a timestamp. Paired with the changed-since read, this is what keeps a mirror exactly in step. - **Check Document Exists** Reports whether the account already holds a file, from its hash and content. The pre-check that stops a reprocessed mailbox from filing the same invoice repeatedly. - **Download Document** Fetches a document as a file into FlowRunner file storage. - **List Attachments** Lists files attached to a document. - **Upload Attachment** Attaches a supporting file to a document. - **Delete Attachment** Removes an attached file. ### Companies and Portals 9 - **List Companies** Lists supplier records. A supplier connected to a portal is maintained by GetMyInvoices itself. - **Get Company** Retrieves one supplier record, including the creditor number that routes an export. - **Create Company** Creates a custom supplier record for a supplier that has no portal behind it. - **Update Company** Updates a supplier record. Setting the creditor number here is what makes the eventual export land in the right account. - **Delete Company** Removes a supplier record. - **List Portals** Lists the supplier portals available to connect to. - **Suggest Portal** Suggests a portal to the vendor for a supplier that is not yet covered. - **Delete Portal Connection** Stops collection from a connected portal. Documents already filed stay, nothing reports an error, and reconnecting needs credentials a person holds. This is the operation this page's human gate exists for. - **Request Reconnect** Asks for a portal connection to be re-authenticated, which is the recovery path when credentials expire. ### Banking 13 - **List Bank Accounts** Lists the bank accounts feeding transactions into the account. - **Update Bank Account Balance** Records a balance against a bank account. - **Archive Bank Account** Archives a bank account so it stops appearing in normal use. - **Delete Bank Account** Removes a bank account and its connection. - **List Transactions** Lists transactions for named bank accounts. At least one account has to be named, because there is no read across the whole account. - **Get Transaction** Retrieves one transaction. A negative amount means money leaving, since the sign carries the direction. - **Create Transaction** Records a transaction that did not arrive through a bank feed. - **Update Transaction** Updates a transaction record. - **Delete Transaction** Removes a transaction record. - **Assign Document To Transaction** Pairs a document to the bank line that paid it. The write at the center of reconciliation. - **List Transaction Documents** Lists the documents already assigned to a transaction. - **Ignore Transaction** Clears a transaction off the reconciliation queue for lines that will never have an invoice, such as transfers or salaries. Reversible, which is why it does not need a gate. - **Set Transaction Tags** Sets the tags on a transaction. The tags sent replace the existing set rather than adding to it. ### Reference 1 - **Get Reference List** Reads the account's reference data, covering countries, currencies, tags, and tax rates in one call. ### Support 1 - **Submit Support Ticket** Raises a support ticket with the vendor from inside a flow, which is useful for capture failures a person will otherwise have to notice first. ## Frequently Asked Questions ### What can FlowRunner do with GetMyInvoices? FlowRunner agents can run Check API Status, Get Account Details, and List Users in GetMyInvoices, plus 36 more actions. ### Does connecting GetMyInvoices to FlowRunner require OAuth? No. GetMyInvoices connects to FlowRunner with an API key, no OAuth flow required. ### Can GetMyInvoices trigger a FlowRunner workflow automatically? GetMyInvoices doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at GetMyInvoices?** This integration exposes GetMyInvoices to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/getmyinvoices. Site index: https://flowrunner.ai/llms.txt