Integrate Accounting Into Freight System
Budget: ₹12,500 – ₹37,500 INR
I built our freight-forwarding solution in .NET with an MS SQL back end, covering everything from enquiries and quotations through to job management, House BL printing, and P&L reporting. The only missing piece is a seamless bridge to external accounting software—this is where I need your expertise.
What I want
• Direct integration between my freight-forwarding database and a well-known accounting package (e.g., Tally, QuickBooks, Xero or a similar platform you can propose).
• Automatic transfer of all financial events we already capture—sales invoices, supplier bills, receivables, payables, and cost allocations—so the books stay in sync without duplicate entry.
• Bi-directional status updates: if an invoice is paid or a journal is adjusted in the accounting system, the change should reflect inside my application.
• Robust error handling and clear logging so any failed sync can be diagnosed quickly.
Tech context
The current stack is C# (.NET 6) with SQL Server 2019. Core financial data is exposed through stored procedures and REST endpoints, so you can choose between direct SQL calls, Web API consumption, or an integration layer written in C#—whichever is most reliable for the target accounting platform’s API or SDK.
Deliverables
1. An integration service (source code plus compiled executable or library) that handles authentication, data mapping, and scheduled sync.
2. Configuration screens inside the existing WinForms interface (or a slim web page, if you prefer) where an admin can enter API keys, toggle modules to sync, and set frequency.
3. Deployment guide and schema changes, if any, in a concise README.
4. Short video walkthrough or live demo proving end-to-end data flow for at least one export and one import cycle.
5. Unit or integration tests covering the critical sync paths.
Acceptance criteria
• A new freight shipment invoice appears in the accounting package within 5 minutes of save.
• Payment status changed to “Paid” in the accounting package updates the local job P&L view on refresh.
• No duplicate records on repeated syncs.
• Error logs are written to a dedicated table and surfaced in the UI.
If you have prior experience integrating ERP or logistics systems with accounting APIs, I’d love to see it. Let’s eliminate the last manual step in our workflow and give users a true one-stop freight management platform.
What I want
• Direct integration between my freight-forwarding database and a well-known accounting package (e.g., Tally, QuickBooks, Xero or a similar platform you can propose).
• Automatic transfer of all financial events we already capture—sales invoices, supplier bills, receivables, payables, and cost allocations—so the books stay in sync without duplicate entry.
• Bi-directional status updates: if an invoice is paid or a journal is adjusted in the accounting system, the change should reflect inside my application.
• Robust error handling and clear logging so any failed sync can be diagnosed quickly.
Tech context
The current stack is C# (.NET 6) with SQL Server 2019. Core financial data is exposed through stored procedures and REST endpoints, so you can choose between direct SQL calls, Web API consumption, or an integration layer written in C#—whichever is most reliable for the target accounting platform’s API or SDK.
Deliverables
1. An integration service (source code plus compiled executable or library) that handles authentication, data mapping, and scheduled sync.
2. Configuration screens inside the existing WinForms interface (or a slim web page, if you prefer) where an admin can enter API keys, toggle modules to sync, and set frequency.
3. Deployment guide and schema changes, if any, in a concise README.
4. Short video walkthrough or live demo proving end-to-end data flow for at least one export and one import cycle.
5. Unit or integration tests covering the critical sync paths.
Acceptance criteria
• A new freight shipment invoice appears in the accounting package within 5 minutes of save.
• Payment status changed to “Paid” in the accounting package updates the local job P&L view on refresh.
• No duplicate records on repeated syncs.
• Error logs are written to a dedicated table and surfaced in the UI.
If you have prior experience integrating ERP or logistics systems with accounting APIs, I’d love to see it. Let’s eliminate the last manual step in our workflow and give users a true one-stop freight management platform.
Related categories:
.NET
Accounting
SQL
C# Programming
Software Development
Web API
Database Management
API Development