Harvest and Xero: project profitability without spreadsheets

Harvest records delivery effort while Xero records the accounting side of project work. Learn how to define profitability, match projects and periods, and investigate missing costs without maintaining a recurring spreadsheet join. Verify available connector fields first, then use restricted payroll files and aggregate reporting where labor cost is needed.

Why do project totals disagree?

Harvest shows hours against work. Xero shows accounting records that may be organized around customers, invoices, bills, and reporting periods. A project can look healthy in one view and weak in another because the two views are measuring different things. Neither total becomes a margin calculation merely by appearing beside the other.

Harvest Xero project profitability starts with a definition. Are you reviewing delivery margin, margin after allocated overhead, or cash collected less cash spent? Those are distinct measures. Pick the question before joining records, and label the result so a payment delay does not accidentally become evidence of unprofitable delivery.

A recurring spreadsheet often hides these choices inside formulas and manual exceptions. Replacing that routine requires more than moving the same totals to another screen. The matching rules, accounting basis, cost boundary, and unresolved exceptions must stay visible. Otherwise, a faster answer can repeat the same misunderstanding every month.

For the wider relationship between paid time and commercial results, read what each employee's time actually earns. This playbook narrows that question to a named time and accounting pair, with payroll evidence added only when the selected margin definition needs it.

What gets joined?

How Harvest and Xero records are joined
In Harvest	In Xero	How they are matched
Project and client	Contact and tracking reference	Reviewed project crosswalk with stable identifiers
Hours, tasks and service dates	Invoice lines and credits	Same project and reporting period
Billable expenses	Supplier bills	Project reference, checked for duplicates
Approved time by team	Payroll file or journal (restricted)	Minimum cost components per period

Begin with project identity. A Harvest project name may not appear as a matching field on every Xero record. Build and review a crosswalk using stable identifiers and approved references where available. A customer match alone is insufficient when that customer has several projects, retainers, or overlapping delivery periods.

The SIGNLD connector directory lists Harvest and Xero, alongside QuickBooks, HubSpot, Salesforce, and Stripe. Listing does not guarantee automatic access to every desired field or complete project mapping. Verify the supported records, selected permissions, historical coverage, and refresh behavior before committing to a particular report.

The intended join brings together these evidence groups, subject to that verification:

Delivery records: project references, service dates, hours, tasks, and approved time where available.
Revenue records: relevant invoice lines, credits, customer references, and finance's chosen recognition treatment.
Expense records: supplier bills and attributable project expenses, with a check for duplicates.
Labor records: approved payroll files containing the minimum cost components and period identifiers needed.
Mapping records: the reviewed relationship between projects, customers, teams, and accounting references.

Gusto and ADP are not listed in the directory. Do not assume a direct connection for either provider. If employee labor cost is part of the question, use restricted payroll files and confirm how their periods align with time records. Do not substitute customer billing rates for employee cost rates.

Missing project references require a visible exception queue. An invoice spanning two engagements may need a finance-approved split. A supplier bill without a project reference should remain unallocated until reviewed. Automated relationships cannot justify inventing an allocation where the underlying records provide no defensible basis.

Which questions should you ask first?

Start with questions that can be checked against a small completed period. A focused review exposes mismatched definitions before the report influences pricing or staffing. Use the following sequence as a numbered investigation, not as a promise that every field will be available from every account.

Which projects have delivery hours but no matched revenue records for the selected period?
Which invoices or credits cover multiple projects and need an approved split?
Which projects have attributable supplier costs that are absent from the current cost view?
Which teams delivered more work than planned after adjusting for agreed scope changes?
Which records remain unmatched, and could those exceptions materially change the apparent margin?

Then calculate a narrowly labeled result. For illustration only, $20,000 of recognized project revenue less $12,000 of attributable labor and $3,000 of supplier cost leaves $5,000 of contribution before excluded overhead. These invented numbers explain the arithmetic. They do not represent a customer result, benchmark, or expected return.

Keep cash collection separate unless cash is the selected question. An unpaid invoice may create a collection risk without changing delivery effort. Equally, a deposit received before work begins does not prove that the future project will be profitable. Ask finance which revenue basis should govern the comparison.

How does SIGNLD support the review?

SIGNLD's Knowledge Graph builds automatically from connected sources, with no data engineering required. Use that connected context to examine relationships across the available records. Human review still matters for ambiguous identities, allocation policy, and accounting treatment. Automatic graph construction is not a guarantee that source records contain complete project detail.

Frame a Decision Topic around a concrete recurring question, such as which active delivery groups need a pricing or staffing review. A Decision Brief can summarize the evidence, assumptions, outstanding exceptions, and proposed next action. Keep the review about project economics rather than employee rankings or surveillance.

Restrict payroll fields to those necessary for costing, and limit detailed access to authorized users. Share project or team aggregates for ordinary management discussion. Exclude bank information, personal tax identifiers, and unrelated personal records. If a tiny reporting group would reveal individual compensation, broaden the group or restrict the audience.

Your data stays yours: read-only connections, a private LLM powered by AWS Bedrock on a single-tenant instance, and we never train on it.

How do you keep the answer trustworthy?

Reconcile one closed period to finance's accepted totals before expanding the review. Check revenue, credits, supplier costs, and payroll allocations independently. Record exclusions and unmatched amounts beside the result. A project margin that omits a late supplier bill should be provisional, not silently presented as final.

Assign ownership for exceptions. Delivery can confirm project scope and time coding; finance can confirm accounting treatment and cost inclusion. Review again after close adjustments. Once definitions are stable, Risk Alerts can support ongoing attention to configured changes, but the team must still decide what requires investigation and what reflects ordinary timing.

The outcome should be an operational choice: revise a quote, address scope drift, change a handoff, or reserve capacity. Keep the original evidence and the decision together so the next review can test whether the intervention helped. Repeated reporting is useful only when someone can explain and act on the differences.

Key takeaways

Harvest and Xero are listed connectors, but available fields and project mappings still need verification.
Match delivery periods and accounting treatment before calculating project profitability.
Use approved payroll files when employee cost is needed rather than assuming direct payroll support.
Keep unmatched records visible and use aggregate results for pricing and staffing decisions.

FAQ

Are Harvest and Xero both listed connectors?

Yes, both appear in the SIGNLD connector directory. That confirms their listing, not automatic access to every record or field you might want. Before designing the report, verify account permissions, available objects, date coverage, and project identifiers. If a needed relationship is missing, document the gap and agree a supported way to supply or review it.

Does connecting them guarantee a complete project margin?

No. Margin depends on your cost definition and whether the available records contain enough detail to apply it. Missing labor costs, unallocated supplier bills, credits, or incomplete project references can change the answer. Keep those exceptions visible and reconcile a closed period before using the result to make recurring pricing or staffing changes.

Where does employee labor cost come from?

Use approved payroll files when payroll cost is needed. Gusto and ADP are not listed connectors, so do not assume direct support for either. Include only necessary employer cost fields and period identifiers, restrict detailed access, and join them to approved time allocation records. Report team or project aggregates rather than individual compensation comparisons.

Can paid invoices replace recognized revenue?

Only if the question is explicitly about cash collection. Payment dates and delivery periods often differ, especially with deposits, milestone billing, or overdue balances. For delivery profitability, use the revenue treatment finance approves and match costs to the same work period. Keep a separate collection view when the team also needs to understand cash exposure.

Try SIGNLD free

Review the connectors, then register for SIGNLD. Choose the Free Forever plan or a 14-day Growth trial, no credit card. Begin with one closed period and a clearly defined project profitability question.