Planning your accounting integration

Proxima runs the field and the depot; your accounting software keeps the books. Proxima Connect links the two so nobody types an order, invoice or payment twice. A short plan before installing saves weeks of clean up.
Decide where each record starts
| Record | Usually starts in | Then |
|---|---|---|
| Customers | Proxima (reps onboard shops) or your books | Matched both ways by account number, tax ID, then name, so nothing is duplicated. |
| Products | Your books or Proxima | Matched by SKU, then name. |
| Orders and invoices | Proxima | Sent to the books as invoices. |
| Returns | Proxima | Sent as credit notes against the original invoice's customer. |
| Payments | Proxima | Sent as customer payments, including wallet use. |
| Purchases | Proxima | Received purchase orders sent as purchase orders and bills. |
| Stock additions and approved expenses | Proxima | Sent as stock adjustments and expenses. |
Sending runs from Proxima to the books. Creating customers, products or suppliers in Proxima from records that exist only in the books is also possible, and is off until you switch it on.
Have these ready
- The date your books start from. Nothing created before it is sent.
- Your tax names and rates, and your cash and bank accounts, as they are in the books.
- Which accounting location or godown each depot maps to.
- A dedicated integration user and licence in Proxima, and a dedicated user in the accounting software.
- A Windows computer or server that stays on, with access to Proxima and the accounting software.
Tip
Clean duplicates in both systems before the first sync. The connector matches carefully, but two copies of the same shop in your books will still be two copies.
Related guides: What Proxima Connect does · Integration licence and user · Server requirements.
Still stuck?
Message our support team on WhatsApp in English, Tamil, Malayalam or Hindi.