Analytics integration
Connect Google BigQuery with Wingspan to track team spend. Send worker records, assignments, and approved work logs to your warehouse. Send payables to track what you owe. Your team can study total spend and project profit. You choose what data to send.
Google BigQuery 
Connect the work to the payment
Google BigQuery
Worker reporting table
Wingspan
Worker records (payees)
Google BigQuery
Engagement and assignment reporting tables
Wingspan
Engagement templates and assignments
Google BigQuery
Requirement status table
Wingspan
Requirements and eligibility
Choose which records sync and when they move. Your team stays in control of work review and payment approval.
Export worker records and payment data to BigQuery. An assignment is a job for one worker. Your team can match labor spend with project income. You can track spend across teams. Compare contractor pay and employee payroll totals in one view.
Export payables and approved work logs into BigQuery. A payable is an amount owed to a worker. Finance teams can forecast cash needs with ease. Track open payables before you give payer approval. This helps you spot cost shifts before money moves.
Export annual 1099 totals and onboarding flags to BigQuery. Your team reviews records across groups and sees readiness for each worker assignment.
Google BigQuery is a cloud data warehouse. Teams use it to report on business data. Connecting Wingspan with BigQuery brings worker spend together for analysis. Wingspan handles worker onboarding, required checks, work logs, and pay. BigQuery stores your data for reports and cost models.
In Wingspan, a worker record is called a payee. You pick the worker type for each person: contractor or W-2 employee. For contractors, Wingspan tracks W-9 checks, bills you owe, and 1099 forms. A payable is a bill you owe to a worker. For W-2 workers, Wingspan runs payroll with tax withholding. Set warehouse access separately from Wingspan user permissions. Choose export tables and sync schedules that fit your reporting goals.
Choose which tool holds each record. Set the changes that sync between them. Connect your records to the Wingspan workflows below.
Worker records (payees)
Wingspan to Google BigQuery
Approved worker records export to a BigQuery table. In Wingspan, a worker record is called a payee. You pick the worker type: contractor or W-2 employee. Your team can query worker counts by team. Adding a worker, sending an invite, and setting pay rules are separate steps.
Engagement templates and assignments
Wingspan to Google BigQuery
Work templates and worker assignments export to BigQuery. An engagement is a reusable work template. It sets agreed rates. An assignment links one worker to a job. One worker can have many assignments. Your team can join assignment terms with project data. This helps you track rates and staffing across teams.
Requirements and eligibility
Wingspan to Google BigQuery
Wingspan exports check status and assignment readiness to BigQuery. The engagement sets the required checks. Wingspan tracks each worker check on the assignment. Contractors use Form W-9 and any required insurance proof. W-2 workers use their own hire and withholding forms. Your team reports on the results.
Work logs and work items
Wingspan to Google BigQuery
Reviewed work items and approved work logs export to BigQuery. Work items record hours, tasks, or units. A work log groups items for one assignment. Approving contractor work creates one amount owed. The worker sees an invoice. The payer sees a payable. Payer approval stays separate. BigQuery reports show costs by project and date.
Payables
Wingspan to Google BigQuery
Contractor payables and approval states export to BigQuery. A payable is an amount owed to a contractor worker. Creating a payable does not send money. A manager must grant payer approval before pay runs. W-2 workers do not use payables. Their pay flows through payroll runs. Your team can track due dates and plan cash needs.
Client invoices and payers
Reference or reporting
Client bills join with worker payables in a BigQuery view. A client bill is money you charge a customer. The customer is the payer on that bill. A payable is money you owe a worker. Your team can query this view to see project profit. Client billing and worker pay stay on separate controls.
Payment status and references
Wingspan to Google BigQuery
Payment dates, methods, and status fields export to BigQuery. Paid is a status in Wingspan. Deposit confirmed means the sending bank or provider finished processing. It does not prove the worker's bank posted funds. Your team uses these records for reports and to match payments to its books.
Tax forms and reporting
Wingspan to Google BigQuery
Contractor 1099 totals and filing status export to BigQuery. W-2 payroll totals stay separate from contractor bills. Your team uses the summaries to review records. Filing stays with the chosen filing owner. A form upload does not complete a tax filing.
01
A manager approves a contractor work log.
A manager approves contractor work in Wingspan. This creates one amount owed. The worker sees an invoice. The payer sees a payable. Approved work and payable records export to BigQuery. Your team compares costs with budgets in reports. In this reporting workflow, your finance team manages payment approval and pay runs in Wingspan.
02
Finance starts a worker pay run.
Finance approves pay in Wingspan. Contractor and W-2 runs stay separate. Payment dates, methods, and status fields export to BigQuery. Your team matches those records with bank statements. Deposit confirmed means the sending bank or provider finished processing. It does not prove the worker bank posted funds. Payment controls stay in Wingspan.
03
Your team issues a client invoice.
Your team sends a client bill in Wingspan for project work. The client acts as the payer on that bill. Linked contractor payables show what you owe workers for the project. Both record sets export to BigQuery. A saved view joins client bills and payables by project code. Finance teams query this view to review profit margins. Client billing and worker pay stay on separate controls.
This guide covers reporting exports from Wingspan to BigQuery. Your team manages worker records, checks, work logs, and payment approval in Wingspan. Warehouse access does not grant access to Wingspan records. Set the export direction and any writeback requirements with our team.
Choose the worker fields to export and who needs access to them. Use BigQuery column policy tags to control access to tagged fields in SQL queries. Set those permissions around your reporting and finance roles.
Set export schedules to fit your reports. Daily exports help match monthly books. Busy teams use more frequent runs. Date partitions help limit the data each query scans. Your team chooses the table design and query rules. Those choices affect speed and cost.
Connect worker records from hire to pay. Choose the Contractor or W-2 type and keep the right checks for each.
Bring worker records, work review, and payments together. We’ll help you set up the flow your team needs.
Discuss your integration