How to connect field sales to your accounting system

How do you connect field sales to your accounting system?

Decide which system owns each type of record, match the codes in both systems, then sync in both directions on a schedule your finance team can check. Most of the effort goes into those decisions and the data cleanup. The technical connection is often the smaller part.

The goal is simple: a rep's order or invoice reaches accounting without anyone typing it again, and the rep sees the right customers, prices and balances. This applies whether you are a distributor or a factory selling through your own reps, such as a water plant running daily routes.

Work through these steps in order.

List the records that need to move, and name one owner for each.
Clean customer and product data, then match the codes across both systems.
Choose the connection: a ready connector, or a build on the API.
Set rules for duplicates, failures and documents created offline.
Pilot on a few routes, reconcile each day with finance, then roll out.

Which records should sync, and in which direction?

A common split is that master data flows from accounting to the field, and transactions flow from the field to accounting. Your accounting system keeps the books, so it usually stays the owner of customer accounts, products, tax codes and price lists. The field app owns what happens at the outlet.

Be careful with anything both sides might edit. If a rep can add a new customer in the app, decide whether that customer waits for approval before it reaches accounting, and who fixes the record if the details are wrong. Write these decisions down, because they are what you will come back to when numbers disagree.

Accounting to field: customers, products, units, tax codes, price lists and open balances.
Field to accounting: sales orders, invoices, returns and credit notes, and cash and cheque payments.
Decide case by case: new customers, promotions and credit limits.
Keep out of the sync: visit notes, route data and photos, unless finance needs them.

How do you match customers and products before you connect?

Give every customer and product one shared code, and fix duplicates before the first sync, because accounting systems reject documents that point to records they do not have. Microsoft's reference for Dynamics 365 Business Central says a sales invoice's customer must exist in the Customer table, and a customer payment's linked invoice must exist in the Sales Invoices table. In SAP Business One, Apideck's integration guide notes that creating an invoice requires a CardCode that references an existing business partner.

Start with an export from each system and compare them. Field teams often have the same shop under two names, and products sold in cartons in the field may be counted in pieces in accounting. Agree on the unit of measure and the conversion now. A carton recorded as a single piece will produce wrong stock and wrong revenue, and the error can take days to find.

Tax needs the same attention. Map each product to the tax code your accountant wants, and have them approve the mapping before you go live.

How do you stop duplicate invoices and lost records?

Give each transaction a unique reference that stays the same on every retry, and keep a visible list of anything that failed. Field apps retry when a connection drops, and a retry without a reference can post the same document twice. Intuit's best practices for the QuickBooks Online API explain this directly: with a unique request ID, the API returns the original response if it has already seen that request. Without one, a duplicate transaction is created.

Failures will happen, usually because a customer code is missing or a period is closed. They should land in a list that someone owns, with a clear reason next to each record. If a failed invoice disappears silently, finance finds out at month end.

Plan for offline work too. A rep may finish a day with no signal, then send a day's documents at once. Keep the original date and time on each document, so sales land in the right day and period. Large batches also meet limits: Intuit recommends staying within 500 requests per minute for each company, and a connection should queue and retry when it reaches a limit.

What changes between QuickBooks, SAP and Dynamics?

The business rules above stay the same, but each system has its own objects and limits, so ask your integrator about these before you estimate the work. SAP and Microsoft each sell more than one product, and the examples here come from SAP Business One and Dynamics 365 Business Central. Confirm the exact edition you run, because the details differ between them.

QuickBooks Online: use a unique request ID on each transaction, and use its webhooks or Change Data Capture to pick up changes, which Intuit recommends over repeated polling.
SAP Business One: the Service Layer is an OData-based API with Orders, Invoices, BusinessPartners and Items. Apideck's guide says sessions expire after 30 minutes of inactivity by default and results return 20 records per page by default, so plan for both.
Dynamics 365 Business Central: a customer payment is a line inside a customer payments journal and cannot be reached directly, and invoices carry a status such as Draft, Open or Paid. Microsoft points new work to version 2.0 of the API.

Where does e-invoicing fit in?

Decide which system issues the legal invoice, and let only that system file it. If the rep prints an invoice at the customer's door, the field app is usually the system issuing it, and accounting should receive a copy of a finished document instead of creating a second one. If two systems issue the same sale, you risk two tax documents for one transaction.

In Saudi Arabia this decision affects your ZATCA setup, which we cover in our guide to ZATCA Phase 2 for van sales. Confirm the final design with your tax adviser, because you remain responsible for your invoices whichever software you use.

How do you test the connection before rollout?

Run a pilot on a few routes for at least one full sales cycle, and have finance reconcile the totals every day. The test passes when the day's sales, returns and collections in the field app match the accounting system to the last unit of currency, with no help from anyone behind the scenes. Include the awkward cases on purpose, because normal days rarely reveal the problems.

A full day with no signal, then a sync at the end.
A return against an earlier invoice.
A part payment, and one payment that covers two invoices.
A cheque recorded in the field and handled later by finance.
A new customer created by a rep.
A price change made in accounting that must reach reps before the next route.

How does Repzo connect to accounting?

Repzo SFA has two-way sync with systems such as QuickBooks, SAP, Microsoft Dynamics and MySQL, so confirmed orders move to the back office without re-entry. Reps issue invoices, apply returns and collect cash and cheque payments in the field, and sales orders, invoices and cash payments can be recorded offline and sync when the phone reconnects. Repzo also has an API for connecting other systems, and it handles e-invoicing with ZATCA in Saudi Arabia and JoFotara in Jordan.

These are Repzo's own product statements. Your edition and setup decide what the connection covers, so ask us to confirm it against your accounting system before you commit. The invoicing page has more detail on the field side.

Frequently asked questions

Do I need an ERP to connect field sales to accounting?

No. The same approach works with an accounting package such as QuickBooks. What you need is a clean customer and product list, and clear ownership of each record. A bigger ERP adds more objects to map, not a different method.

Should invoices be issued in the field app or in accounting?

If reps hand over an invoice at the door, issue it in the field app and send the finished document to accounting. If invoices are issued at the office after delivery, send the order from the field and issue the invoice in accounting. Choose one, because two systems issuing the same sale creates two documents.

How long does it take to connect a field app to accounting?

It depends mostly on your data. Clean codes and a ready connector shorten the work, while duplicate customers, mixed units or a heavily customised system lengthen it. Ask for an estimate after you have compared the exports from both systems.

What happens if a record fails to sync?

It should stay in a visible list with the reason, and someone in finance or operations should own that list. Common causes are a missing customer code, an unmapped product or a closed accounting period. Fix the cause, then send the record again using the same reference.

Does Repzo connect to QuickBooks, SAP and Microsoft Dynamics?

Yes. Repzo SFA has two-way sync with systems such as QuickBooks, SAP and Microsoft Dynamics, and an API for other systems. Editions differ, so confirm yours with our team before you commit.