Description
Summary ## What this is We run a multi-tenant SaaS (AGR Bridge) that already has a working QuickBooks Web Connector (QBWC) SOAP endpoint and full backing schema (14 qb_* tables, approximately 4,000-line Deno edge function). We need an experienced QBWC integrator with a real Windows and QuickBooks Desktop environment to finish the on-prem hardening and ship a signed .QWC package. This is not a from-scratch build. The scaffolding is done. You are finishing clearly enumerated TODOs and proving it works end-to-end against a live QB file. If you are the right person, this is a week of focused work. ## What we've already built SOAP endpoint (supabase/functions/qb-web-connector/index.ts) All 14 tables: qb_web_connector_config, qb_sync_queue, qb_sync_log, qb_sync_cursors, qb_entity_mappings, qb_pending_reviews, qb_transactions, qb_items, qb_classes, qb_ar_aging, qb_pnl_summary, qb_pnl_by_account, qb_account_snapshots, plus configuration. Developer console at /dev/qb-desktop (Overview, Configuration, Connection Test, Company/Entity Mapping, Sync Logs, Web Connector Status, Diagnostics, Import/Export Test) qbXML cheatsheet and full TODO backlog ## What you finish Ticket lifecycle (issue, refresh, expiry, replay guard), credential validation, proper connectionError and getLastError responses, Content-Type and SOAPAction validation Signed .QWC package plus Windows installation and uninstallation documentation Implementation of the "preview" and "ping" actions Formal retry backoff and dead-letter behavior on qb_sync_queue End-to-end verification against our sandbox QuickBooks company file for Customer, Vendor, Item, Invoice, Bill, Purchase Order, Check, and Journal Entry Historical backfill using QBWC_BACKFILL_DAYS Password hash storage upgrade ## Milestones **Milestone 1** SOAP hardening and signed .QWC package Payout: $300 Target: Days 1–3 **Milestone 2** Preview and ping actions, queue policy Payout: $300 Target: Days 3–5 **Milestone 3** On-prem end-to-end validation and handoff Payout: $400 Target: Days 5–7 ## Requirements Prior shipped QBWC integration (please include a link) Your own Windows and QuickBooks Desktop (Enterprise or Pro) test environment Ability to sign a .QWC package with a code-signing certificate (self-signed for development, Intuit-approved for production) Comfortable working with TypeScript and Deno edge functions Async communication with one weekly sync call At least three hours per day of overlap with U.S. business hours ## What we provide A complete development kit so you can begin on day one with minimal back-and-forth Staging edge function URL and dedicated test tenant (fabricated data only) A sandbox QuickBooks company file (no real client data) GitHub branch-scoped write access Lovable project-scoped collaborator seat Fast pull request reviews (typically within 24 business hours) ## What to expect after you apply Within 24 hours, Alex Popiela (our Development Coordinator) will reply with either a decline or a brief three-question screening. Within 48 hours, we'll schedule a 20-minute introductory call. No live coding. The same day the contract is accepted, you'll receive repository access, the development kit, and the sandbox QuickBooks company file. On Day 1, you'll create a qbwc/kickoff branch and submit a one-page implementation plan. Our target is completion by Day 7, with a hard deadline of Day 14. Once Milestone 3 is merged, final payment will be released and a 30-day bug-fix warranty begins. ## Protections you agree to All work will be completed on qbwc/* branches. The main branch is protected. Only the sandbox tenant and sandbox QuickBooks company file may be used. No production client data leaves AGR. No AI training on our codebase or documentation. Standard work-for-hire intellectual property assignment under Upwork Terms. Access will be revoked after Milestone 3 is merged. ## To apply Provide a link to a prior QBWC project you shipped. Include one sentence describing your QuickBooks Desktop test environment (edition and year). Ask any clarifying question that is not already answered in the development kit. Please do not submit AI-generated cover letters. Begin your reply with the word **qbwc-ready** so we know you read the posting.