QuickBooks API Integration VB.NET
Budget: $30 – $250 USD
I already have a working VB.NET solution that downloads every QuickBooks Online master file and writes them into a SQL Server database. The schema is set and will be shared, along with the existing source, so you can build on top of it rather than starting from scratch.
Your job is to extend that solution to cover our remaining day-to-day transactions:
• Invoices
• Payments received
• Bills
• Bill payments
• Journal entries
What I need from you
1. Add the necessary OAuth 2.0 flow (our current module authenticates but you may need to refresh tokens automatically).
2. Call the relevant QBO endpoints, handle paging, and pull only records modified since the last sync.
3. Map each JSON payload cleanly into the provided MSSQL tables, re-using our helper methods for inserts/updates.
4. Build sturdy error handling and logging so retries don’t create duplicates.
5. Deliver well-commented VB.NET code that compiles in Visual Studio, along with a concise read-me explaining any new app settings, scopes, or stored procedures you added.
Acceptance criteria
• A one-click console run (or scheduled task) brings all five transaction types into SQL Server with no unhandled exceptions.
• Source passes a quick peer review for clarity and follows normal Microsoft naming conventions.
• A sample data pull on my QBO sandbox shows records correctly related to their customers, vendors, and accounts.
I’ll give you: current solution, DB schema script, and client ID/secret for a sandbox company. You give me: updated VB.NET project files, any new SQL scripts, and short deployment notes.
Looking forward to getting this sync fully automated.
Your job is to extend that solution to cover our remaining day-to-day transactions:
• Invoices
• Payments received
• Bills
• Bill payments
• Journal entries
What I need from you
1. Add the necessary OAuth 2.0 flow (our current module authenticates but you may need to refresh tokens automatically).
2. Call the relevant QBO endpoints, handle paging, and pull only records modified since the last sync.
3. Map each JSON payload cleanly into the provided MSSQL tables, re-using our helper methods for inserts/updates.
4. Build sturdy error handling and logging so retries don’t create duplicates.
5. Deliver well-commented VB.NET code that compiles in Visual Studio, along with a concise read-me explaining any new app settings, scopes, or stored procedures you added.
Acceptance criteria
• A one-click console run (or scheduled task) brings all five transaction types into SQL Server with no unhandled exceptions.
• Source passes a quick peer review for clarity and follows normal Microsoft naming conventions.
• A sample data pull on my QBO sandbox shows records correctly related to their customers, vendors, and accounts.
I’ll give you: current solution, DB schema script, and client ID/secret for a sandbox company. You give me: updated VB.NET project files, any new SQL scripts, and short deployment notes.
Looking forward to getting this sync fully automated.