# Sage Intacct integration: invoices, bills and payments > Invoices, carrier bills and payments sync between Roadmark and Sage Intacct, both ways. An invoice posts when you approve it. URL: https://roadmark.ai/integrations/sage Language: en Last updated: 2026-10-01 **TL;DR:** Roadmark syncs invoices, carrier bills and payments with Sage Intacct, both ways. An invoice posts to Sage Intacct when a person approves it, and a multi-entity company maps each Roadmark company to its own Sage Intacct entity. ## What syncs One row for each kind of record: which way it moves, and when. | What | Direction | When | | --- | --- | --- | | Invoices | Both ways | When you approve one, synced in real time | | Carrier bills | Both ways | Once matched and approved | | Payments | Both ways | Automatically, after either system records one | ## Setting up Sage Intacct 1. **Authorize Roadmark in Sage Intacct:** A company admin turns on the Web Services subscription, then adds Roadmark's sender ID under Web Services authorizations on the Security tab of the company setup, with its status set to Active. 2. **Map your companies to entities:** For a multi-entity company, map each Roadmark company to its Sage Intacct entity, or to the top level if its lists are shared. 3. **Choose what syncs:** Turn on invoices, carrier bills and payments, or leave any of them off. 4. **Test with a real load:** Approve one invoice and one carrier bill, and check what came across to Sage Intacct before you turn it on for everything. ### Before you start - A Sage Intacct company with the Web Services subscription enabled. - A Sage Intacct admin who can authorize a Web Services sender ID for the company. - For a multi-entity company: which entity, or the top level, each Roadmark company should post to. ## What posts to Sage Intacct, and when Invoices, carrier bills and payments sync to Sage Intacct, both ways, so nobody re-types an approved number or reconciles a spreadsheet on Fridays. Roadmark reaches Sage Intacct through its [Web Services API](https://developer.intacct.com/web-services/), the interface Sage provides for integrations to create and read invoices, bills and payments. Here's one invoice, from the example load used across this site. All amounts on this page are in US dollars. Load 48213, Mississauga ON to Joliet IL for Prairie Foods, delivered with the POD signed at 18:00 CT. The Billing agent drafted invoice INV-10442 at 18:15: the $4,215.00 on the rate con ($3,655.00 linehaul plus $560.00 fuel) and $100.00 of detention from the ELD, for $4,315.00. J. Park approved it, and it posted to Sage Intacct at 18:21. When Prairie Foods pays it, that payment syncs back and closes the invoice in Roadmark too. ## Carrier bills: matched before they post A carrier's bill is checked against the rate con it was tendered at and the POD before it's approved. On load 48254, Pinecrest Carriers billed $1,940.00 against a $1,780.00 rate con: two hours of detention where the POD shows one billable hour. Roadmark drafted a payment of $1,860.00 and a dispute of $80.00, with the POD attached, for a person to approve. Once approved, the payment posts to Sage Intacct as a bill against Pinecrest, so what Sage Intacct shows as owed matches what was actually approved, not what was billed. ## Multi-entity companies Sage Intacct's [multi-entity setup](https://www.intacct.com/ia/docs/en_US/help_action/Multi-entity/multi-entity-company-overview.htm) puts a top level over one or more entities: the top level holds data shared across all of them, such as customers, vendors and the chart of accounts, while each entity posts its own transactions. In a group of several companies, [Groups](https://roadmark.ai/groups) explains that each keeps its own customers, carriers and books, and a load hauled by one company for another posts as an internal invoice, a payable at one company and a receivable at the other, matched automatically. If a company in the group runs its books on Sage Intacct, its share of that internal invoice maps to its own entity, so the group's structure in Roadmark lines up with the entity structure in Sage Intacct rather than one shared ledger. ## Connecting Sage Intacct To connect, a Sage Intacct admin turns on the Web Services subscription (Company → Admin → Subscriptions) and [authorizes Roadmark's Web Services sender ID](https://www.intacct.com/ia/docs/en_US/help_action/Company/Company_setup/Company_Information/Security/company-web-services-authorizations.htm) for the company (Company → Setup → Configuration → Company, on the Security tab, under Web Services authorizations, with the status set to Active). The authorization belongs to a Sage Intacct company, not an entity: a multi-entity company authorizes Roadmark once for all its entities, while separate Sage Intacct companies each authorize it, the same way each [QuickBooks](https://roadmark.ai/integrations/quickbooks) company or Xero organisation would. Moving billing to Roadmark doesn't mean moving your books. Your books stay in Sage Intacct, synced both ways, whether or not you move invoicing and carrier bills to Roadmark. See [Billing](https://roadmark.ai/billing) for invoices on POD, the three-way match on carrier bills, settlement statements and collections, and [Brokers](https://roadmark.ai/brokers) for how a brokerage's own books stay separate from a carrier's in the same group. ## Driver and owner-operator settlements A load also produces a third line of paperwork: the driver or owner-operator's pay. Roadmark drafts that settlement from the same load as the invoice, with a statement showing every load, its share of revenue, the fuel surcharge, each deduction and the escrow balance, so the driver can check it before a person approves it. That settlement doesn't post to Sage Intacct as an invoice or a bill; it's paid the way settlements are today, while the customer invoice and the carrier's bill keep syncing to Sage Intacct as described above. ## Before you start Connecting Sage Intacct doesn't change how a load is quoted, dispatched or tracked; it only changes where the resulting paperwork lands. Turn on invoices, carrier bills and payments together, or one at a time, and run a real load through it first. Approving one invoice and one carrier bill, then checking both sides in Sage Intacct, is a better test than trusting the connection with a week of billing straight away, and it's a natural place to confirm each company posted to the entity you expected. ## Questions about Sage Intacct and Roadmark ### Does it sync both ways? Yes. Invoices, carrier bills and payments all sync both ways: Roadmark posts an approved invoice or bill to Sage Intacct, and a payment recorded in either system updates the other. ### What happens to payments? A payment applied against an invoice or a carrier bill, in Roadmark or in Sage Intacct, syncs to the other side automatically, so an invoice shows as paid in both places without anyone re-entering it. ### Does it work with a multi-entity company? Yes. Sage Intacct's multi-entity setup has a top level holding lists shared across entities, such as customers and the chart of accounts, with each entity posting its own transactions. Each Roadmark company maps to its own Sage Intacct entity, or to the top level. ### Are carrier bills checked before they post to Sage Intacct? Yes. Each carrier bill is checked against the rate con it was tendered at and the POD before it's approved. A bill over the rate con waits with a drafted payment and dispute instead of posting in full. ### When does an invoice post to Sage Intacct? When a person approves it. Roadmark drafts the invoice when the POD arrives, and a person approves the numbers instead of typing them. On the example load 48213, INV-10442 was drafted at 18:15 and posted at 18:21. ## Related pages - [Billing and settlements](https://roadmark.ai/billing): Invoices, driver pay and carrier pay - [Groups of companies](https://roadmark.ai/groups): Companies, divisions and sister rates - [Brokers and 3PLs](https://roadmark.ai/brokers): Quote, cover, track and bill - [NetSuite integration: invoices, bills and the ledger](https://roadmark.ai/integrations/netsuite): Invoices, vendor bills and journal entries post from Roadmark to NetSuite once you approve them, by subsidiary for a OneWorld group. - [Xero integration: invoices, bills and payments](https://roadmark.ai/integrations/xero): Invoices, carrier bills and payments sync between Roadmark and Xero, both ways. An invoice posts to Xero when you approve it. Companies, people and shipment figures in product examples are fictional. They illustrate workflows and are not customer testimonials or measured results.