Project Management

Harvest

< Back to All Connectors
Connect your AI to Harvest
Project managers, finance and billing teams, and agency and firm owners run hours, budgets and invoices through Harvest, but the answers they need sit across time entries, projects, expenses and estimates that each live on their own screen. AI can pull those together in seconds, but only if it surfaces hourly rates, cost rates and invoice amounts to people entitled to see them and treats locked, billed or closed entries as final.

‍

Start a Trial
Get a Live Demo

Why it matters

Capabilities that matter most for Harvest

01

Hours, budgets and billing in one answer

Ask one question and get time entries, project budgets, expenses, estimates and invoices together instead of opening a report per screen.
02

Rates and costs stay protected

Hourly rates, cost rates and invoice amounts are only surfaced to people entitled to see them, and locked, billed or closed entries are treated as final.
03

Ready-made Harvest tools and prompts

25 read-only Get data tools and 10 read-only prompts, such as weekly timesheet reviews, project budget health and unbilled work, are available from the app store.
03

Combine Harvest with your CRM and ERP

Cross-system prompts compare Harvest with Salesforce, HubSpot, NetSuite, Business Central and more, so billing is checked against deals and ledgers in one place.

Use cases

Example AI Use Cases for Harvest

Filters

scenario

-

At the end of the week a manager opens each person's timesheet one at a time to see who is short of hours, then scrolls the entries for timers left running, entries nobody has approved and lines with no notes. On a busy team a gap or a timer that ran overnight is easy to miss until approval day.

What popdock provides

--

Name a week start and optionally one person, and it lists the active people with their weekly capacity, then compares the hours each has logged with that capacity. It flags running timers, entries that are not approved, entries with no notes and single entries over 12 hours. Contractors are reported separately and not chased for capacity. If a name matches more than one person it lists them and stops. Nothing is approved or edited, and cost and billable rates are never shown.

Business outcome

---

You know who to chase before the week is approved, with gaps, stray timers and unapproved entries listed per person and no rates exposed.
See Full Use Case

scenario

-

Accounts receivable staff scan the invoice list for anything past due, then open each client to see which payments have arrived and dig through messages to learn who was already reminded. It is slow, and a part-paid invoice or a client chased twice in one week is easy to miss.

What popdock provides

--

Give an as-of date, and optionally one client, and it finds open invoices past their due date with a balance still owing and works out the days overdue. For each client it adds the payment history, the reminders already sent and when, and the contact to write to. Each invoice is tagged as not yet reminded, reminded and silent, or partially paid, with totals per client and overall. Nothing is changed, no reminder is sent and no payment is recorded.

Business outcome

---

You see which overdue invoices need a first reminder, a second nudge or a payment check, grouped by client with totals and nothing sent.
See Full Use Case

scenario

-

Quotes sent through Harvest sit in different states, and nobody has a running view of which are waiting on a client and which have gone quiet. Sales and account teams page through estimates, work out the win rate in a spreadsheet and count days since sending by hand.

What popdock provides

--

Give a number of months and optionally a client, and it groups recent estimates by state with a count and value for each. It works out the win rate from accepted against accepted plus declined, and flags sent estimates that have waited more than 14 days. For the five largest it shows what is being quoted, and it notes declined estimates above the average value. Nothing is sent to clients and nothing is changed.

Business outcome

---

Quotes waiting on a client are listed with days waiting and amount, so the right follow-ups happen before deals go cold.
See Full Use Case

scenario

-

Matching invoices to payments and line items is done one invoice at a time: add up the payments, compare with the balance, then total the line items against the invoice amount. Across a month of invoices, a paid invoice with a balance or an invoice with no lines can sit unnoticed.

What popdock provides

--

Give a period, and it pulls the invoices issued, matches the payments by invoice number and checks that the amount less payments equals the balance due. It then totals the line items per invoice and compares them with the invoice amount, saying when a difference could be tax or a discount rather than calling it an error. Only the exceptions are listed, each with what was compared and the difference. Nothing is corrected, recorded or deleted.

Business outcome

---

Billing exceptions are found in one pass, with the numbers behind each, so you fix real errors without rechecking every invoice.
See Full Use Case

scenario

-

Project managers go through budget reports one project at a time and only see an overrun once the money is spent. Working out how many weeks are left at the current pace, and whether a fixed-fee project is a margin problem or a time-and-materials one is a billing conversation, takes manual maths.

What popdock provides

--

Give an optional client and a risk threshold (80 percent by default), and it ranks active projects that have used at least that share of their budget. For each it takes this month's hours to estimate the weeks left at the current pace, then checks the fee type and end date to suggest an action such as raise a change order, slow the burn or bill now. Monthly budgets are not compared with lifetime spend, and projects with no budget are listed separately instead of guessed. Budgets and project settings are never changed.

Business outcome

---

Projects heading for an overrun are ranked with weeks left and a suggested action, so you act while there is budget left.
See Full Use Case

scenario

-

To see who is stretched and who has room, operations leads export the team time report, copy it into a spreadsheet and work out capacity for the period, utilization and billable ratio per person. Contractors muddy the numbers, and the reasons behind the extremes need another trip into assignments.

What popdock provides

--

Give a period, and it takes each person's total and billable hours against weekly capacity multiplied by the weeks in the period. It works out utilization and billable ratio, reports contractors separately and flags people over 100 percent, under 60 percent or with a billable ratio under 50 percent. For the two highest and two lowest it shows what they are assigned to, and it ends with who could take more work. Rates are never shown and nothing is changed.

Business outcome

---

Overloaded and under-used people are visible side by side with their assignments, so you rebalance work from the numbers.
See Full Use Case

scenario

-

Billable time and expenses only become revenue once someone invoices them. Finance teams export time and expenses and match them to invoices by hand, so approved work for one client can wait weeks while another is billed, and entries that are not yet approved get mixed in.

What popdock provides

--

Give a period and optionally a client, and it pulls the uninvoiced report with hours, amount and expenses per client, largest first. For the five largest it lists the billable time entries and expenses not yet billed, and notes which entries are not approved and may not be invoiceable yet. The result shows the oldest unbilled date and the three clients to invoice first. Amounts are never added across currencies, and no invoice is created.

Business outcome

---

Billable work waiting to be invoiced is listed by client with the oldest dates, so billing starts with the biggest gaps.
See Full Use Case

scenario

-

Before a client call, an account manager opens five Harvest screens for projects, hours, invoices, estimates and contacts, then pieces them together. A late invoice or an estimate waiting for an answer is easy to miss in all the clicking.

What popdock provides

--

Give a client name and, optionally, a number of months, and it finds the client by exact name, stopping with a list of matches when the name is unclear. It then gathers projects with fees and budgets, hours and billable amounts, invoices with billed, paid and outstanding totals, estimates and contacts. You get an overview, a projects table, invoices with late ones highlighted, estimates pending and contacts, followed by a few observations such as slow payment or a project near budget. Cost rates are never shown and nothing is changed.

Business outcome

---

You walk into a client call with one account summary and the issues flagged, after asking once.
See Full Use Case

scenario

-

Before billing day, an admin clicks through each active project to check for a budget or fee, an hourly rate, a code, billable task rates and a project manager. Projects with no one assigned or no rate only show up when an invoice comes out wrong.

What popdock provides

--

Give an optional client, and it checks active projects for a missing budget and fee, a billable project without an hourly rate, and a missing code. It then checks task assignments for projects with none and for billable tasks with empty rates, and people assignments for projects with no project manager or no one assigned. You get one row per problem project with its gaps, grouped by client, plus counts per type of gap. It only reports. Nothing is fixed or changed.

Business outcome

---

Setup gaps are listed per project before billing day, so invoices and reports are not built on missing rates or owners.
See Full Use Case

scenario

-

Reviewing expenses means paging through long lists for large amounts, items without notes, items nobody approved and billable costs that were never invoiced. The totals by category, person and project need separate reports, so the picture takes a long time to assemble.

What popdock provides

--

Give a period and optionally an amount threshold, 500 by default, and it summarizes spend by category with total and billable amounts, and lists the top five people and projects. It then finds single expenses at or above the threshold, along with billable expenses not yet invoiced, and flags those not approved or with empty notes. The exception list shows user, project, amount, date and the reason flagged. Expenses are never approved, edited or deleted.

Business outcome

---

Large, unapproved, undocumented and unbilled expenses are listed with reasons, so review time goes to the items that matter.
See Full Use Case

scenario

-

Chorus calls them accounts and Harvest calls them clients, and the only link between the two is the customer name. Leaders compare the lists by eye to learn which customers talked to sales but never became clients, and which billed clients have gone quiet in sales conversations.

What popdock provides

--

Give a period, or accept the last 90 days, and it reads the accounts that appear in Chorus conversations and the active clients in Harvest with their hours and billable amounts. It matches names exactly first, then loosely when one name contains the other, and marks each pair as exact, loose or unmatched. You get three lists: Chorus accounts with no Harvest client, Harvest clients with billable hours and no Chorus conversations, and loose matches to confirm. A name match is a suggestion, never proof. If either side returns nothing it says so, and nothing is changed in either system.

Business outcome

---

Customers missing from billing and clients missing from sales conversations are listed, with loose matches flagged for a person to confirm.
See Full Use Case

scenario

-

As people join and leave, licenses in the call recorder and accounts in the time tracker drift apart. IT compares the Chorus user list with the Harvest user list by hand, and names spelled differently make it easy to pair the wrong person.

What popdock provides

--

Give a period, or accept the last 30 days, and it reads the active users in Chorus with their license, role and team, and the active users in Harvest with their capacity and hours. It matches the two lists on email address only, ignoring case, never on name. You get counts first, then who is in both, who is only in Chorus and who is only in Harvest with hours, flagging anyone with hours but no Chorus user. Harvest users without an email are listed separately, cost rates are not shown and nothing is changed.

Business outcome

---

Accounts that exist in only one system are listed with hours, so licenses and users can be tidied from a reliable email match.
See Full Use Case

scenario

-

Before chasing an overdue invoice, finance rarely knows whether the customer is mid-negotiation with sales or has a live issue. Chorus calls them accounts and Harvest calls them clients, so checking means looking up each name in both systems, and a reminder can land at the wrong time.

What popdock provides

--

Give a minimum number of days overdue (14 by default) and a Chorus look-back window (60 days by default), and it finds open Harvest invoices past that mark and totals the amount due per client. For up to 10 clients, largest first, it finds the latest Chorus conversations and emails by client name, and says how many clients were not looked up. The table shows total due, oldest due date and last conversation. It only calls a conversation a dispute when the text says so, and it never drafts or sends a reminder. Nothing is changed.

Business outcome

---

Overdue invoices are paired with recent sales conversations, so reminders go out with context and at a sensible moment.
See Full Use Case

scenario

-

People who join sales calls with a customer are recorded in Chorus, but they are often never added as contacts in Harvest. Invoices and estimates then go to the wrong person, and finding the gap means reading call participants and comparing emails with the client's contacts by hand.

What popdock provides

--

Give a client name and, optionally, a start date, and it finds that client's Chorus conversations and stops to ask if several account names match. It reads the external participants on up to 15 conversations, merges duplicates by email and compares them with the client's Harvest contacts. You get who is already in Harvest and who is missing, with the number of conversations attended and the latest date. Matching is on email only, people without an email are mentioned, and it says how many conversations were not read. Nothing is added or changed.

Business outcome

---

Customers who join calls but are missing from billing contacts are named with their email, ready for you to add.
See Full Use Case

scenario

-

Account owners flip between the call recorder and the billing system to see whether sales activity lines up with invoices and hours. The two never share an id, so matching one customer by name is slow and easy to get wrong.

What popdock provides

--

Give a client name and, optionally, a look-back in days (90 by default), and it finds the account in Chorus, stopping to ask if more than one name matches. It then finds the client in Harvest by name, and reports a customer missing from either system instead of guessing. You get Chorus activity, with conversations, last date, owners, open opportunities and emails, beside Harvest billing, with invoiced, due, hours and uninvoiced amounts. It adds up to three observations that need both together, states the date window and shows how the name was matched. Nothing is changed.

Business outcome

---

One customer's sales and billing picture arrives in a single answer, with the date window and name matching shown.
See Full Use Case

scenario

-

To find Harvest invoices that never reached the ERP, accounts staff scroll the Harvest invoice list and search Dynamics 365 Business Central for each number one at a time, then check whether the customer even exists there. It is slow, drafts and voids get mixed in, and the gaps usually surface only at period close.

What popdock provides

--

Give a start date and optionally a client name, and it lists the sent or paid Harvest invoices from that date, then checks Dynamics 365 Business Central for a posted document and for an unposted one. Missing invoices are grouped by client with a subtotal and whether the customer exists, so you know if one must be created first. Draft and void invoices are left out, and if Business Central returns no posted invoices at all it warns that the matching number may not be filled in instead of calling everything missing. Nothing is created or changed in either system.

Business outcome

---

You see exactly which Harvest invoices still need booking, and what they total, well before the books close.
See Full Use Case

scenario

-

Project managers hold the budget in Harvest while job costing sits in Dynamics 365 Business Central. When someone asks how a project is tracking, they open both, find the matching job by hand and compare spend and budget lines side by side, often mixing hours with currency amounts.

What popdock provides

--

Name a Harvest project and it reads the project's budget, spend and remaining amount, finds the matching Dynamics 365 Business Central job, and totals the job's budget and usage lines. It shows both sides together, the difference in spend, whether the client and bill-to customer look like the same party, and whether the job is complete or blocked while the project is still active. If the project name matches more than one project it stops and lists them, and if no job exists it says so rather than guessing. When the Harvest budget is in hours, only hours are compared. Nothing is changed.

Business outcome

---

You get a single side by side view of Harvest budget and job costing, with differences called out and no guessed matches.
See Full Use Case

scenario

-

To see what a client owes, collections staff open Harvest and Dynamics 365 Business Central side by side and add up open items in each. The two totals rarely agree, and finding out why means matching invoices by number and digging through ledger entries, often for an hour per client.

What popdock provides

--

Give a client name and it reads that client's open Harvest invoices, finds the matching Dynamics 365 Business Central customer, and reads its balance and open posted invoices. It shows the total due in each system, the difference, and the invoices open in one system but not the other, matched by invoice number. If the gap remains it looks at ledger entries for unapplied items or credits. It flags a blocked or over-limit customer, never converts currencies, and stops when more than one customer matches. Nothing is updated.

Business outcome

---

You can explain a client receivable gap in minutes, with the invoices behind it named and no figures converted or guessed.
See Full Use Case

scenario

-

Before a billing run, billers total the uninvoiced work per client in Harvest, then look up each client in Dynamics 365 Business Central for holds, overdue balances and credit limits. When this is skipped or rushed, clients that should not be billed yet get invoiced anyway.

What popdock provides

--

Give a period, or leave it for last month, and optionally a minimum amount or client name. It reads the uninvoiced Harvest work grouped by client, finds each matching Dynamics 365 Business Central customer, and gives every client a verdict: ready to bill, over credit limit, customer blocked, overdue balance or no customer. It sorts by uninvoiced amount, treats a zero credit limit as unset and lists amounts in different currencies separately instead of summing them. It never creates an invoice in either system. Billing stays your decision.

Business outcome

---

You start the billing run knowing which clients are ready and which need attention first, with no invoice created along the way.
See Full Use Case

scenario

-

Someone exports the Harvest client list and the Dynamics 365 Business Central customer list and compares them by eye, with names that differ by Inc, LLC or punctuation. Clients billed in one system and missing from the other go unnoticed until an invoice has nowhere to land.

What popdock provides

--

It reads the active Harvest clients and the Business Central customers, optionally narrowed to names containing a word you give. Names are matched ignoring case, punctuation and company suffixes, and never on a partial word. You get three lists: clients with no customer, customers with no active client, and matched pairs showing whether the customer is blocked and its balance. A client matching several customers is listed as ambiguous, a truncated list is flagged as partial, and if a side returns nothing it stops. Nothing is created or edited.

Business outcome

---

Clients missing from either system are found in one pass, with ambiguous matches shown for you to decide rather than guessed.
See Full Use Case

scenario

-

At month end someone ticks Harvest invoices off against Dynamics 365 Business Central postings by hand, one number at a time. Invoices that never posted, sit unposted, or were posted with a different amount are found late, after the books are already being closed.

What popdock provides

--

Give a date range, or use the last 30 days, and optionally a client. It reads the Harvest invoices in the range, skipping drafts, and finds each one in Business Central by invoice number among posted invoices, then among unposted documents. You get one table with a status for each: matched, amount differs, paid in one system only, unposted, or missing, plus counts and the total difference. Differences under a cent count as matched, an invoice matching several documents is reported as ambiguous, and nothing in either system is created or changed.

Business outcome

---

Month end reconciliation of invoices takes one request, with missing, unposted and mismatched items named and counted.
See Full Use Case

scenario

-

Before a client call someone opens the account in Dynamics 365 Sales, then Harvest, then the invoices in each system. Even then an unpaid bill, a stack of unbilled hours or an open support case can be missed, and it changes how the conversation should go.

What popdock provides

--

Give a client name and a look-back period, and it finds the client in Harvest and the account in Dynamics 365 Sales, stopping if either name is ambiguous. From Harvest it reads invoices, uninvoiced work, tracked hours and project budgets. From Dynamics 365 Sales it reads open opportunities, open cases and invoices with an amount due. The brief is split into billing, work, pipeline and support, labels each figure with its source system, and ends with up to five things to watch. Hourly rates are hidden unless you ask. Nothing is changed.

Business outcome

---

You walk into a client call knowing billing, work in progress, pipeline and support in one brief, with each figure tied to its source.
See Full Use Case

scenario

-

Finance copies invoice totals out of Harvest and Dynamics 365 Sales into a sheet to check that the two agree. Invoices that exist on one side only, amounts that differ, or an invoice paid in one place and still open in the other are easy to miss in a long list.

What popdock provides

--

Name a client and a start date and it reads that client's Harvest invoices and its Dynamics 365 Sales invoices. Pairs are matched by the invoice number in the CRM invoice name, or by amount and an issue date within a week, and each is marked exact, amount differs, or paid in one and unpaid in the other. You then see Harvest invoices not in the CRM, CRM invoices not in Harvest, and the totals billed and outstanding in each. Different currencies are listed as a mismatch, not compared, and it never says which system is right. Nothing is edited.

Business outcome

---

Invoice differences between Harvest and the CRM are listed by pair and by gap, without a copied sheet or any record being edited.
See Full Use Case

scenario

-

Project managers often learn that a deal was won only when the client asks about kickoff, because nobody checks Dynamics 365 Sales against Harvest for new work. Matching won opportunities to Harvest clients and projects by hand means going through two systems name by name.

What popdock provides

--

Give a date, and optionally a client name, and it lists the opportunities won in Dynamics 365 Sales since then. For each customer it checks Harvest for a client and for a project. You get three groups: won deals whose customer has no Harvest client, deals with a client but no project, and deals that already have a project. Topic, customer, revenue, close date and owner are shown, with counts. Matches are by name only and it says so, and it stops if there are no won deals. No client or project is created.

Business outcome

---

Won deals that still need a Harvest client or project are found before the client asks about kickoff.
See Full Use Case

scenario

-

A Dynamics 365 Sales quote and the Harvest estimate for the same piece of work are kept by different people. Over time the amounts and statuses drift, such as an estimate accepted in Harvest while the CRM quote is still open, and nobody notices.

What popdock provides

--

Name a client and optionally a start date, and it reads that client's Harvest estimates and Dynamics 365 Sales quotes. An estimate is paired with a quote when the subject and quote name share key words or the amounts are equal, and guessed pairings are marked as guesses. You see each pair with its amount difference and both statuses, then estimates with no quote and quotes with no estimate. If several client names appear it stops, and it does not compare amounts across currencies. No estimate or quote is edited.

Business outcome

---

Estimates and quotes that have drifted apart are found and listed, with any guessed pairing labelled as such.
See Full Use Case

scenario

-

Someone exports the client list from Harvest and the account list from Dynamics 365 Sales and compares them by eye in a spreadsheet. Clients that are billed with no CRM account, and accounts with no matching client, go unnoticed because names differ by suffix or punctuation.

What popdock provides

--

It reads the active Harvest clients and the Dynamics 365 Sales accounts, up to a record limit you can set, optionally narrowed to names containing a word. Names are matched ignoring case, punctuation and suffixes such as Inc, LLC and Ltd, and near matches are shown as possible rather than exact. You get clients with no account, accounts with no client marked informational, and possible matches side by side, with counts. Truncated lists are flagged, and it stops when either side returns nothing. Nothing is created or updated.

Business outcome

---

Billing clients without a CRM account, and the reverse, are listed in one pass, with near matches kept apart from exact ones.
See Full Use Case

scenario

-

Collectors chase overdue invoices from Harvest without knowing the client also has an open support case or a deal about to close in Dynamics 365 Sales. The call goes badly, because the wider relationship is only visible after switching to a second system.

What popdock provides

--

Give a minimum number of days overdue and optionally a client, and it lists the overdue open Harvest invoices with days overdue and totals. For each client it then reads the open opportunities and open cases in Dynamics 365 Sales. You get one block per customer, largest overdue total first, with a handle with care note when there is a high-priority case or a late-stage deal. A client with no CRM match is labelled no CRM account found rather than assumed to have no deals. It sends no reminders and hides rates. Nothing is changed.

Business outcome

---

Collectors see the open deals and cases behind each overdue client before they call, so reminders land with the full picture.
See Full Use Case

scenario

-

Cash is recorded against Harvest invoices by one person and applied to receivables in Dynamics GP by another, and nobody checks that the two agree. A payment recorded in one system and never applied in the other, or applied for a different amount, can sit unnoticed for weeks.

What popdock provides

--

Give a client name and a start date, and it reads the payments recorded in Harvest for that client, then finds the single matching Dynamics GP customer and reads its receivables applications. Payments are matched by invoice number and amount, and partial payments on one invoice are added together first. You see Harvest payments with no application, applications with no payment, pairs where the amount differs, and the total on each side. It stops if the customer is not exactly one match. No payment is recorded, corrected or deleted in either system.

Business outcome

---

Payment gaps between Harvest and the ledger are listed by invoice, so cash recorded in one place cannot go unapplied in the other.
See Full Use Case

scenario

-

Billing staff tick a client's Harvest invoices against Dynamics GP receivables line by line. Invoices that never reached the ledger go unnoticed until collections, and matching is awkward because the number may sit in the document number, the sales order number or the customer PO field.

What popdock provides

--

Name a client and a start date, and it reads the Harvest invoices from then, ignoring drafts, and finds the single matching Dynamics GP customer. It reads that customer's receivables documents and sales documents and matches each invoice by number, falling back to the customer PO number, and states how matches were made when formats differ. You get a table with a verdict of matched, amount differs or missing in GP, a list of GP documents with no Harvest invoice, and totals for each side. It stops if the customer is missing or ambiguous. Nothing is changed.

Business outcome

---

Invoices missing from the ledger or posted for a different amount are found per client, with the matching method stated.
See Full Use Case

scenario

-

Hours are entered twice, once in the time tracker and once on the Dynamics GP project timesheet, and the totals quietly drift apart. The difference is usually found at payroll or billing time, after someone has added up each project by hand in both systems.

What popdock provides

--

Give a person's name and a date range, and it totals that person's Harvest hours per project, then finds the matching employee in Dynamics GP by last name and checks the first name agrees. It reads their timesheet lines for the same dates, totals the quantity per project and matches projects by name. You get a table of Harvest hours, GP hours and the difference per project, projects on one side only, timesheets still unposted and overall totals. If the employee is not unique, or the units are not hours, it stops or says so. Nothing is changed.

Business outcome

---

Time entered twice is compared per project in one request, so hour differences surface before payroll and billing.
See Full Use Case

scenario

-

Someone exports the Harvest client list and the Dynamics GP customer list and compares them by eye. The two systems share no id, so names that differ by a suffix or a comma hide clients billed in one system and missing from the other until an invoice cannot be matched.

What popdock provides

--

Optionally name a client to focus on, or check all active clients. It reads the Harvest clients, looks each one up in Dynamics GP by name, and ignores case, punctuation and suffixes such as Inc or Ltd. You get clients with no customer, clients that match several customers with every candidate shown, and matched pairs where the name or the inactive and hold flags disagree. Nothing is changed in either system, and it never guesses when two customers fit.

Business outcome

---

Gaps between Harvest clients and Dynamics GP customers surface in one report, with probable matches kept apart from confirmed ones.
See Full Use Case

scenario

-

Project managers read budget and spend in Harvest, then open Dynamics GP for costs and billings and subtract in a spreadsheet. Because the figures sit in two systems with different currencies and dates, overruns are found late.

What popdock provides

--

Name a project and it reads the Harvest budget, spend, uninvoiced and invoiced amounts, then finds the Dynamics GP project of the same name or code. You see Harvest figures beside Dynamics GP forecast cost, actual cost and actual billings, with a flag where invoiced and billed differ by more than your tolerance (5 percent by default) or the client or dates disagree. It stops if either project is missing or ambiguous, does not convert currencies, and changes nothing.

Business outcome

---

Budget, cost and billing for one project line up on a single view, so overruns and billing gaps are spotted before they grow.
See Full Use Case

scenario

-

At the end of the week people rebuild their calendar and meeting notes to log meeting time in Harvest. Meetings get forgotten, so hours that were worked never reach a timesheet.

What popdock provides

--

Name a person and a date range (the last 7 days by default) and it finds them in Harvest, reads their Granola meetings and their logged time, then checks each meeting against entries on the same date. Each meeting is marked covered, partly covered or not covered, with the entry that covers it, and a guessed match is labelled probable. Billed entries are treated as final and rates are not shown. Nothing is created or edited.

Business outcome

---

Meetings with no time logged are listed with their hours, so timesheets can be completed without rebuilding the week by memory.
See Full Use Case

scenario

-

Finance hears about work in a client meeting but cannot easily tell whether it was logged and invoiced. Answering means finding the meeting notes, working out who attended, finding the client in Harvest, then checking time, unbilled work and invoices.

What popdock provides

--

Give part of a meeting title and it finds the Granola meeting, reads its attendees and follows their emails to a Harvest client, with a fallback on the title words. It then shows hours logged within a week either side of the meeting by project, billed and unbilled hours, the uninvoiced amount and the latest invoices with state. It stops on an ambiguous meeting or client, never creates invoices, and hides rates.

Business outcome

---

You can answer whether the work from a client meeting was logged and billed without opening three screens.
See Full Use Case

scenario

-

Before a client call someone digs through old meeting notes, then separately through Harvest for budget, uninvoiced work, invoices and hours. The notes and the numbers are never read together, so the points that matter get missed.

What popdock provides

--

Name a Harvest client and a lookback period (60 days by default). It finds the client, uses its contacts to locate the past Granola meetings, and pulls project budget, uninvoiced hours and amount, open or overdue invoices and recent hours. The brief lists meetings with one line summaries, budget used and remaining, billing position and talking points tied to a figure. It stops on an ambiguous client, marks title-only note matches as unconfirmed, hides rates and changes nothing.

Business outcome

---

You walk into the client call with the meeting history and the commercial position in one brief, ready for the budget and billing conversation.
See Full Use Case

scenario

-

External people keep turning up in meetings but are never recorded as client contacts. Finding them means reading each meeting's attendees, dropping your own staff and checking every address against Harvest.

What popdock provides

--

Optionally filter by meeting title and choose a lookback (30 days by default). It reads the Granola meetings and their attendees, removes anyone who is a Harvest user, then checks each remaining email against Harvest contacts. You get known contacts with their client, and people not in Harvest with the meetings attended and a likely client by email domain. Free mail domains are ignored for that guess, and no contact is created.

Business outcome

---

Everyone you meet is either a known contact or on a list to add, with a likely client suggested, so client records keep pace with meetings.
See Full Use Case

scenario

-

To see whether a client's sales pipeline and billing line up, someone opens estimates and invoices in Harvest and deals in HubSpot and adds them up by hand. Currencies and states differ, so a won deal with no invoice goes unnoticed.

What popdock provides

--

Name a client and a start date (the start of this year by default). It finds the client in Harvest and totals its estimates and invoices by state, including billed, paid and outstanding. It then finds the matching HubSpot company and lists its deals by stage with amounts. A short list of mismatches follows, such as a won deal with no estimate or invoice. It stops if the client name is ambiguous, still reports billing when HubSpot has no match, and shows currency with every amount.

Business outcome

---

One client's billing and pipeline sit side by side with mismatches called out, so leadership sees where revenue and deals disagree.
See Full Use Case

scenario

-

Contact details drift between the billing system and the CRM. Nobody notices until an invoice goes to a stale address or a CRM contact has no billing record.

What popdock provides

--

Optionally name a client to focus on and a record limit (200 per system by default). It reads the Harvest contacts and the HubSpot contacts and matches them on email only, ignoring case and spaces. Contacts without an email are listed separately instead of guessed. You get who is in Harvest only, in HubSpot only, and in both with differing names or company, showing both values, plus counts. It warns when a list hit the limit and changes nothing.

Business outcome

---

Billing contacts and CRM contacts are compared on email, so stale addresses and missing records are found before an invoice goes astray.
See Full Use Case

scenario

-

Someone exports clients from Harvest and companies from HubSpot and compares the two lists by eye. Near-duplicate names and records that exist in only one system are easy to miss.

What popdock provides

--

Optionally filter by part of a name and set a record limit (200 per system by default). It reads active Harvest clients and HubSpot companies and matches names ignoring case, punctuation and suffixes such as Inc or LLC. A name contained in another is shown as a possible match, not counted as exact. You get clients with no company, companies with no client, and possible matches side by side, with counts. It warns when a list hit the limit and never creates or updates a record.

Business outcome

---

Clients and companies that exist in only one system are found, with near-duplicate names set apart as possible matches.
See Full Use Case

scenario

-

Finance chases overdue invoices from Harvest, then switches to the CRM to find who owns the account, who to email and whether a deal is in play. It repeats one client at a time, so the chase is slow and uninformed.

What popdock provides

--

Optionally set an as-of date and a minimum amount due. It lists open Harvest invoices past due, grouped by client, then finds each client in HubSpot. For every matched company it adds the owner, up to 3 contacts with email, open deals with stage and amount, and the latest notes. Clients are listed most overdue first. It never picks a company when several match, says No HubSpot match when there is none, and changes no invoice or CRM record.

Business outcome

---

Each overdue client comes with who to contact and what deals are open, so collection calls start informed and in order of urgency.
See Full Use Case

scenario

-

Finance staff compare the Harvest client list with the Sage Intacct customer list by eye. Clients without a customer, and customers without a client, go unnoticed until an invoice fails to post.

What popdock provides

--

Name a client, or check all active clients up to 100. It reads the Harvest clients and the Sage Intacct customers and matches on name, ignoring case, punctuation and suffixes, since the systems share no id. Matches are marked exact or probable, and when several customers fit it lists the candidates instead of choosing. You get clients with no customer, customers with no client and probable matches that differ, then counts. It stops if either side is empty, says when a cap makes it partial, and writes nothing.

Business outcome

---

Missing, extra and mismatched records between Harvest and Sage Intacct are found before they cause a failed invoice posting.
See Full Use Case

scenario

-

Payments recorded against Harvest invoices have to be found again among Sage Intacct customer payments. Unrecorded or mismatched payments are easy to miss in a month-end hand check.

What popdock provides

--

Give a start date (30 days back by default) and optionally a client. It reads the Harvest invoice payments and the Sage Intacct customer payments, then matches by customer, amount and a date within 5 days, and also tries the transaction reference. Several candidates are listed rather than chosen, and one Intacct payment equal to several Harvest payments is reported as a batch match. You get unmatched payments on each side, matched pairs that differ and the unmatched totals. It stops if a read is empty and writes nothing.

Business outcome

---

Payments that never reached Intacct, or differ from Harvest, are listed with totals, so cash is matched before month end closes.
See Full Use Case

scenario

-

Projects are set up twice, once in Harvest and once in Sage Intacct. Nobody notices when the client, dates or budget differ or when a project exists on one side only.

What popdock provides

--

Name a client, or check all clients. It reads active Harvest projects and the Sage Intacct projects, matches the Harvest code to the Intacct project id, then falls back to the name, and compares client, dates and the Harvest fee or budget against the contract amount. It states whether a Harvest budget is in hours or money before comparing. You get projects missing on each side and matched pairs that differ, with counts. If a client has no Intacct customer it continues with the Harvest side only, and it writes nothing.

Business outcome

---

Project setup differences between Harvest and Sage Intacct are listed in one report, so budgets and dates are corrected before billing.
See Full Use Case

scenario

-

Hours logged in Harvest and hours entered on Sage Intacct timesheets are compared by hand, per person and project. Gaps surface only at payroll or billing time.

What popdock provides

--

Give a period (the last full week by default) and optionally a person. It reads Harvest time entries and Sage Intacct timesheet entries, totals hours per person and project on each side and matches people by name regardless of case or order. You get a table per person with Harvest hours, Intacct hours and the difference, flagging gaps over a quarter hour and anyone or any project on one side only. Intacct entry states are shown rather than dropping unapproved entries, and it says when a record cap makes totals partial. Nothing is written.

Business outcome

---

Hour gaps between Harvest and Intacct timesheets are visible by person and project, with the largest gaps first, before payroll or billing runs.
See Full Use Case

scenario

-

Invoices raised in Harvest are re-keyed or imported into Sage Intacct, and finance checks the two lists by hand. Missing invoices and amounts or balances that drifted are easy to overlook.

What popdock provides

--

Give a start date (90 days back by default) and optionally a client. It reads the Harvest invoices, skipping drafts, and finds each in Sage Intacct by invoice number, then reference, then customer and amount as a probable match. It compares amount and balance, and flags paid in one system but still due in the other. You get invoices in one system only and matched pairs that differ, with both values, counts and the amount at stake. It never converts currencies, stops if either side is empty, and writes nothing.

Business outcome

---

Invoices missing or out of step between Harvest and Sage Intacct are listed with the amount at stake, so the receivables ledger can be corrected.
See Full Use Case

scenario

-

Expenses are logged in Harvest so they can be billed to clients, and filed in NetSuite so people get reimbursed, and it is easy to do one and forget the other. Finance lines up two exports by hand to find who has expenses in one system and no expense report in the other.

What popdock provides

--

Give a date range, and optionally part of a name, and it reads expense totals by person from Harvest and expense reports from NetSuite. People are matched by name, ignoring case and name order, with email used to confirm borderline cases. You get three lists: Harvest expenses with no NetSuite report, NetSuite reports with no Harvest expenses, and people in both with the Harvest total and the report number and status. Nothing is changed in either system, rates stay hidden, and it stops if one side returns nothing.

Business outcome

---

Missing expense reports and unlogged expenses show up in one read-only pass, before reimbursements or client billing go out wrong.
See Full Use Case

scenario

-

When a client disputes a balance, someone opens Harvest and NetSuite, adds up the open invoices in each and tries to explain why the two totals differ. Unapplied payments, credits and invoices open in only one system make the gap hard to trace by hand.

What popdock provides

--

Name a client and it finds the open invoices in Harvest and the matching customer and unpaid invoices in NetSuite. It gives the Harvest total, the NetSuite invoice total and the NetSuite customer balance, then matches invoices by number and lists the ones that explain the difference. You can ask it to include credits and unapplied payments, which it labels as such rather than calling them errors. It stops if the client name matches more than one, nothing is changed in either system, and if the currencies differ it shows both totals without subtracting.

Business outcome

---

A disputed balance gets a line by line explanation from both systems, so the conversation with the client starts from facts.
See Full Use Case

scenario

-

Billing runs through Harvest and the ledger runs through NetSuite, and the client lists drift apart. Someone exports both and compares names by eye, so a client billed in one system and missing from the other goes unnoticed.

What popdock provides

--

Optionally give part of a name and it reads active clients from Harvest and customers from NetSuite. Names are matched ignoring case, punctuation and suffixes such as Inc, LLC and Ltd, and a name that only contains the other is shown as a possible match instead of an exact one. You get three lists: Harvest clients with no NetSuite customer, NetSuite customers with no Harvest client, and possible matches side by side, with a count for each. Nothing is changed, it stops if either side is empty and it warns when a list may be truncated.

Business outcome

---

Clients missing from either system are found in minutes, with exact and possible matches kept apart so you confirm only the uncertain ones.
See Full Use Case

scenario

-

Hours are entered in Harvest and again in NetSuite for project accounting, and nobody checks that the two agree until the project is closed. By then the differences are spread across people and weeks and take a long time to untangle.

What popdock provides

--

Name a project and a date range and it reads the hours tracked in Harvest, total and billable, and the time recorded in NetSuite, then groups both by person. People are matched by full name ignoring case. You see each person with Harvest hours, NetSuite hours and the difference, anyone present in only one system, and the project totals. Differences under a quarter of an hour are ignored, NetSuite time that is not approved is labelled by status, rates are not shown and nothing is changed. It stops if the project name matches several projects.

Business outcome

---

Hour differences between Harvest and NetSuite are caught during the project, not at close, with the people behind them named.
See Full Use Case

scenario

-

Month-end tie-out of Harvest invoices to the NetSuite ledger is done line by line in a spreadsheet. A missing or mistyped invoice is easy to overlook and is often found weeks later, when someone asks why revenue does not agree.

What popdock provides

--

Give a date range, and optionally part of a client name, and it reads invoices issued in that period from Harvest and NetSuite. Invoices are matched by number after trimming spaces and leading zeros, and when no number matches it tries the same client and amount within a week and labels it as matched by amount. You get Harvest only, NetSuite only and amount differences with counts and totals. Draft Harvest invoices are ignored and counted, amounts in different currencies are not compared, empty or truncated results are flagged, and nothing is changed.

Business outcome

---

Missing and mistyped invoices are found at month end instead of weeks later, with every mismatch listed by invoice number.
See Full Use Case

scenario

-

Before a client call or renewal, someone pulls billing from Harvest, then the balance and open invoices from NetSuite, and stitches the two views together by hand. Unbilled work and budget left are easy to forget, and the pieces take a long time to collect.

What popdock provides

--

Name a client and, optionally, how many days to look back, and it finds the client in both systems, stopping if the name matches more than one. It then builds a brief with Harvest invoices, unbilled work and project budget remaining, and the NetSuite balance, unpaid invoices and sales orders with their status. It ends with a watch list of anything overdue, over budget or where the open amounts differ by more than 1 percent. Currencies are kept apart, rates are hidden, empty sections say none found and nothing is changed.

Business outcome

---

Client conversations start with billing, balance and unbilled work from both systems in one brief, without a morning of gathering.
See Full Use Case

scenario

-

Collections staff chase overdue Harvest invoices without knowing the customer is in the middle of negotiating a new deal in Nutshell. The account owner then hears about the chase from an unhappy customer. Matching a Harvest client to a Nutshell company by hand takes lookups in both systems.

What popdock provides

--

Give a number of days overdue, 30 by default, and it lists open Harvest invoices past that mark grouped by client. For each client it looks up the Nutshell company by name and adds the owner, last contact and open leads with their value and expected close. Clients with open leads worth more than the overdue total are flagged as handle with care. Each match is labelled exact or partial, ambiguous companies are left unresolved, and nothing is sent, recorded or changed in either system.

Business outcome

---

Overdue invoices are chased by the right person with the sales context in view, so sensitive deals are not put at risk.
See Full Use Case

scenario

-

Account owners switch between Nutshell and Harvest to see whether open deals line up with what a customer owes and how much work is going into them. With no shared id between the systems, it is easy to match the wrong company to the wrong client.

What popdock provides

--

Give a customer name, and optionally how many days to look back, and it finds the company in Nutshell, then its open leads and contacts. It looks up the matching Harvest client by name and shows invoiced and due amounts, hours, billable hours and unbilled work. If the name matches several companies it asks which one, and it reports a customer missing from either system instead of guessing. The report shows how the name was matched, ends with observations that need both systems, and changes nothing.

Business outcome

---

One side by side view of pipeline and billing for a customer, matched by name with the match shown, so account conversations rest on both.
See Full Use Case

scenario

-

Closed deals reach billing by email or memory, so a new customer is sometimes invoiced late or not at all because nobody set up the client in Harvest. Finance has to read the won deals in Nutshell and check each company in Harvest by hand.

What popdock provides

--

Give a won date range, the last 30 days by default, and it reads the leads won in Nutshell in that period. For each company on those leads it checks Harvest clients by name and lists the ones with no client yet, with lead number, name, company, value, closed date and owner. Leads that already have a client are listed with the matched name, loose or ambiguous matches are shown instead of chosen, and leads with no company are reported separately. Nothing is created or changed in either system.

Business outcome

---

New customers get a Harvest client before the first invoice is due, because every won lead without one is on a list.
See Full Use Case

scenario

-

Customers are exported from Nutshell and clients from Harvest and compared in a spreadsheet, and the two lists drift apart between exports. Prospects, renamed companies and duplicates make a by eye comparison unreliable.

What popdock provides

--

Optionally give part of a name and it reads companies from Nutshell and active clients from Harvest. Each pair is marked exact, loose where one name contains the other, or unmatched, and it does not guess beyond that. You get companies with no client, most leads first, clients with no company, and loose matches side by side to confirm, with a count for each. Nothing is changed, it stops if either side is empty, warns on truncated lists and labels companies without a client as informational.

Business outcome

---

Differences between the CRM and billing lists are listed with loose matches kept for a person to confirm, so cleanup starts from a short list.
See Full Use Case

scenario

-

Account owners switch between OnePageCRM and Harvest to see whether open deals line up with what a customer owes and how much work is going into them. With no shared id, matching the right company to the right client by name is easy to get wrong.

What popdock provides

--

Give a customer name, and optionally a look back in days, and it finds the company in OnePageCRM, then its contacts with next actions and its deals with amount and expected close. It looks up the matching Harvest client by name and adds invoiced and due amounts, hours, billable hours and unbilled work. It asks which company when several match, reports a customer missing from either system instead of guessing, shows how the name was matched and changes nothing in either system.

Business outcome

---

One view of deals, next actions and billing for a customer, with the name match shown, so account reviews use both systems.
See Full Use Case

scenario

-

Collections staff chase overdue Harvest invoices without knowing the customer is mid negotiation on a new deal in OnePageCRM. The account owner learns about it from a frustrated call. Finding each client in the CRM by hand means a search for every name.

What popdock provides

--

Give a number of days overdue, 30 by default, and it lists open Harvest invoices past that mark, grouped by client. For each client it looks up the OnePageCRM company by name and adds the contacts with their owners, next actions and dates, and the open deals with amount and expected close. Clients with open deals worth more than the overdue total are flagged as handle with care, ambiguous company matches are left unresolved, and nothing is sent, recorded or changed in either system.

Business outcome

---

Overdue invoices are chased with next actions and open deals in view, so collections do not collide with a live sale.
See Full Use Case

scenario

-

Closed deals reach billing by email or memory, so a new customer is sometimes invoiced late or not at all because nobody set up the client in Harvest. Someone has to read the won deals in OnePageCRM and check each company in Harvest by hand.

What popdock provides

--

Give a won date range, the last 30 days by default, and it reads the deals won in OnePageCRM in that period. For each company it checks Harvest clients by name and lists deals with no client, with deal name, company, amount, close date and owner. Deals that already have a client are shown with the matched name, loose or ambiguous matches are listed instead of chosen, and deals with no company are reported separately. Nothing is created or changed in either system.

Business outcome

---

Every won deal without a Harvest client lands on a list, so new customers can be billed from the start.
See Full Use Case

scenario

-

Customers are exported from OnePageCRM and clients from Harvest and compared in a spreadsheet, and the lists drift apart between exports. Prospects, renamed companies and near duplicates make comparing by eye unreliable.

What popdock provides

--

Optionally give part of a name and it reads companies from OnePageCRM and active clients from Harvest. Each pair is marked exact, loose where one name contains the other, or unmatched, with no guessing beyond that. You get companies with no client, those with the most pending deals first, clients with no company, and loose matches side by side, with a count for each. Nothing is changed, it stops if either side is empty, warns on truncated lists and labels a company with no client as informational.

Business outcome

---

Gaps between the CRM and billing lists are found with loose matches left for a person to confirm, so cleanup starts from a short list.
See Full Use Case

scenario

-

Joiners and leavers are handled in the billing system and the CRM separately, so people end up with a seat in one and not the other, and owner reports do not line up. Checking means listing users in both systems and comparing emails by hand.

What popdock provides

--

Choose active users, the default, or all users, and it reads Harvest users and looks each one up in Pipedrive by email address, comparing emails ignoring case. If an email finds nothing it tries the last name and reports a possible match with a different email, marked for you to check. You get matched people, people in Harvest only and people in Pipedrive only, with contractors noted since they often have no CRM seat. Nothing is changed or deleted in either system and cost and billing rates are not shown.

Business outcome

---

Users missing from Harvest or Pipedrive are listed by email, so seat and owner reporting gaps are found without a manual comparison.
See Full Use Case

scenario

-

Harvest holds the clients you bill and Pipedrive holds the companies sales works with, and the two lists drift apart over time. Finding the client that was never added to the CRM, or the organization with won deals and no billing record, means reading two long lists side by side and squinting at spellings like Contoso Ltd and Contoso Limited.

What popdock provides

--

Optionally give a start date and a record cap, and PopdockAI reads your active Harvest clients and looks each one up by name in Pipedrive. It retries with a looser name search, treats differences in case, punctuation or a suffix such as Inc or Ltd as near matches and shows both spellings. It also lists Pipedrive organizations with won deals that have no Harvest client. Nothing is created, renamed or merged in either system, near matches are left for a person to decide, and it tells you when the cap limits the check.

Business outcome

---

Both systems are checked against each other in one pass, so missing and misspelled customers are found without any record being changed on your behalf.
See Full Use Case

scenario

-

Before a customer call someone opens Harvest for invoices and budgets, then Pipedrive for deals and contacts, and stitches the two together by hand. The brief is easy to get wrong, and it often misses that the customer is behind on invoices or has no open deal at all.

What popdock provides

--

Name a customer and PopdockAI finds the client in Harvest and the matching organization in Pipedrive. From Harvest it reads recent invoices, uninvoiced work and active project budgets, and from Pipedrive the open and won deals and the contacts. It stops to ask if a name matches more than one record and reports a missing match instead of guessing. Amounts are always shown with their currency and never added across currencies, and nothing is changed in either system.

Business outcome

---

You walk into the customer call with billing and sales in one page, including the observations that only show up when both are read together.
See Full Use Case

scenario

-

Collections staff work from a list of overdue invoices in Harvest, but the customer may have a deal in negotiation or a live conversation in Pipedrive. Without checking, a payment reminder lands in the middle of a sales discussion, and the call is awkward for everyone.

What popdock provides

--

Say how many days overdue counts and PopdockAI reads the open Harvest invoices past that point, grouped by client with the amount due. For each client it finds the Pipedrive organization, then lists open deals, the latest notes and the contact names. Clients missing from Pipedrive are marked as such instead of guessed, and amounts are totalled per currency. It does not draft or send any reminder and nothing is recorded in either system.

Business outcome

---

Collections calls go out with the sales context in hand, so overdue invoices are chased without stepping on an open deal.
See Full Use Case

scenario

-

When a Pipedrive deal is marked won, nobody checks that the customer has been set up for billing. Work then starts with no client, estimate or project in Harvest, and the gap is only noticed when the first invoice cannot be raised.

What popdock provides

--

Say how many days back to look, and optionally which owner, and PopdockAI reads the recently won Pipedrive deals. For each deal it looks up the customer in Harvest and checks for estimates and project budgets. Each deal is labelled no client, client only, client with estimate or client with active project, with the unstarted ones first. A customer name that matches several clients is marked ambiguous rather than chosen. It creates no clients, estimates or projects.

Business outcome

---

Won deals that nobody has started billing are on your list within days, not discovered when the first invoice is due.
See Full Use Case

scenario

-

Account managers usually learn that a project is about to run out of budget when the delivery team complains. By then nobody has opened a renewal or expansion deal, and the customer has already felt the squeeze.

What popdock provides

--

Optionally set what share of budget counts as nearly spent, and PopdockAI reads active Harvest project budgets and keeps those under the threshold, including any already over. For each customer it looks for the organization in Pipedrive and checks for an open deal. The result shows budget, spent and remaining with the unit, and marks each as open deal, no open deal or not in Pipedrive, with ambiguous organizations flagged. Hours and money budgets are never compared, and no deals or leads are created.

Business outcome

---

Customers close to exhausting a budget and without a deal become a short follow up list before the project stalls.
See Full Use Case

scenario

-

Cash application is checked by lining up payment lists from Harvest and the Rillet ledger by hand. A payment recorded in only one place, or with a different amount or date, can stay hidden until the books are closed.

What popdock provides

--

Give a payment date range and PopdockAI reads Harvest invoice payments and Rillet invoice payments for it. It ties each Rillet payment back to an invoice number, then matches payments on invoice number, equal amount and dates within 3 days, using each payment only once. You see payments in only one system and matched pairs whose date or amount differ, with counts and totals per currency. Payments pointing to an unknown Rillet invoice are listed as unresolved. Nothing is created, edited or deleted.

Business outcome

---

Payments recorded in only one system, or recorded differently, are found before the books close, with no entry touched.
See Full Use Case

scenario

-

The time tracking tool and the accounting system each keep their own customer list, and they drift apart. Someone compares names by eye to find clients that were never set up for invoicing, and variations like trading names or a shared contact email make it easy to miss a link.

What popdock provides

--

Optionally narrow by part of a name or include inactive clients, and PopdockAI reads Harvest clients and contacts and Rillet customers and customer emails. It matches in a fixed order, on name ignoring case and punctuation, then on the Rillet invoicing name, then on a shared contact email, and records which rule matched. You see matched clients, Harvest clients with no Rillet customer, Rillet customers with no Harvest client and ambiguous candidates. It never picks between candidates and creates or edits nothing.

Business outcome

---

Every client is confirmed as having a ledger customer, and every gap is listed, without comparing two customer lists by eye.
See Full Use Case

scenario

-

Checking whether a client's tracked work lines up with the contract and invoices in the ledger means pulling reports from Harvest and from Rillet. The comparison is then rebuilt by hand, and a difference in invoiced totals, contract value or currency is easy to miss.

What popdock provides

--

Give a Harvest client and a period, and PopdockAI reads billable hours and amounts by project, uninvoiced work and invoiced totals from Harvest. It finds the matching Rillet customer by name or invoicing name, then reads that customer's contracts, invoices and ARR waterfall. It stops on a missing or ambiguous client or customer and shows the Harvest figures alone when there is no match. The result is a short comparison with plain words on where the figures disagree, per currency, with no conversion and nothing changed.

Business outcome

---

You see where tracked work, invoices and contract value disagree for one client, without rebuilding the comparison from two reports.
See Full Use Case

scenario

-

At month end finance exports invoices from Harvest and from the accounting ledger and compares them line by line in spreadsheets. A missing invoice, a different total, a mismatched currency or an invoice paid in one system and open in the other is easy to slip past.

What popdock provides

--

Give an issue date window, and optionally one client, and PopdockAI reads Harvest invoices, skipping drafts and counting them separately, and Rillet invoices for the same window. It matches by invoice number and falls back to client, amount and date for probable matches, then compares total, amount due and currency. You get four short lists with counts and the difference per currency. Duplicate invoice numbers are listed rather than guessed, currencies are never summed together, and nothing is written to either system.

Business outcome

---

Missing, mismatched and unpaid-in-one-system invoices are found in one pass at month end, with no spreadsheet matching.
See Full Use Case

scenario

-

Sales tracks deals as Salesforce opportunities while delivery sends estimates from Harvest, and nobody checks that the two agree. Accepted work can be missing from the pipeline, or a deal in negotiation can sit with no estimate behind it.

What popdock provides

--

Name a customer and PopdockAI reads that customer's Harvest estimates and its Salesforce opportunities. It pairs each estimate with the opportunity whose name resembles the subject and whose amount is within 10 percent, labelling every pair strong or weak and listing candidates instead of choosing when several fit. You see paired items, contradictions such as accepted in Harvest but not won in Salesforce, open estimates with no opportunity and opportunities in proposal or negotiation with no estimate. Nothing is changed in either system.

Business outcome

---

Disagreements between estimates and opportunities surface in one view, so the pipeline and delivery records tell the same story.
See Full Use Case

scenario

-

Understanding one customer means opening Salesforce for opportunities and cases and Harvest for projects, hours and billing. Leaders end up with an incomplete picture before a renewal or a call, and a case or an unbilled balance is easy to overlook.

What popdock provides

--

Name a customer, and optionally a time window, and PopdockAI finds the account in Salesforce and the client in Harvest, stopping if either name matches more than one record. It reads open opportunities and cases from Salesforce, and active projects, hours, outstanding invoice balances and unbilled work from Harvest. The summary adds a few observations that appear only when both sides are read together. Amounts are shown with their currency, never added across systems, missing data is reported as no data and nothing is changed.

Business outcome

---

You get one summary of relationship, delivery and billing for a customer, with no screens to juggle before a renewal or call.
See Full Use Case

scenario

-

Client contacts are entered separately in Harvest and in Salesforce, so the two lists differ. Finding who is missing from which system is slow, and invoices and updates end up going to stale or incomplete contact lists.

What popdock provides

--

Name a Harvest client and PopdockAI reads its contacts, then looks up each email address in Salesforce, lowercasing both before comparing. Contacts with no email are looked up by name and account and marked as weak matches. The report shows each contact as found, not found or weak, the Salesforce account, differences in title or phone, contacts sitting under a different account and how many have no email. Lookups stop at 25 contacts, with a note of how many remain, and nothing is created or updated.

Business outcome

---

Missing and misplaced contacts are found for a client in one pass, so billing and updates reach the right people.
See Full Use Case

scenario

-

Billing teams chase unbilled Harvest work without knowing that the same customer has an escalated case or a deal in negotiation in Salesforce. An invoice then goes out at an awkward moment, and nobody saw the account situation behind the number.

What popdock provides

--

Set a minimum unbilled amount and PopdockAI reads the Harvest uninvoiced report, totals unbilled work per client and keeps the top 10. For each it finds the Salesforce account and reads open opportunities and open cases. The table shows unbilled amount, projects, open opportunities with count and value and open cases with the highest priority, with a call-out where billing should be careful. Several matching accounts are listed rather than chosen, and no invoices or tasks are created.

Business outcome

---

Billing is prioritised with the account situation in view, so large unbilled balances are handled at the right moment.
See Full Use Case

scenario

-

Invoices are raised in Harvest while customer billing is tracked in Salesforce, and finance matches the two by hand. Amount and paid-status differences slip through, particularly when invoice numbers do not line up exactly or currencies differ.

What popdock provides

--

Name a customer and a start date, and PopdockAI reads that customer's Harvest invoices and its Salesforce invoices and payments. It matches by invoice number, ignoring case and leading zeros, and tries purchase order or subject against the document number for weaker matches, which it flags. You see mismatches in amount, balance and status, invoices found in only one system and totals for each system with the net difference. Currencies are flagged and never converted, differences under 0.01 are noted as rounding and nothing is edited.

Business outcome

---

Amount and paid-status differences between invoices in two systems surface in one report, with no invoice or payment altered.
See Full Use Case

scenario

-

Customer records live in both Harvest and Salesforce, and checking that a client, its account and its contacts agree means opening both tools and comparing by eye. Gaps in names, currency or contact lists go unnoticed until something is sent to the wrong person.

What popdock provides

--

Name a customer and PopdockAI finds the Harvest client and the Salesforce account, stopping to list the options if a name matches more than one record. It compares names, flagging small spelling differences such as Acme Inc against Acme, Inc., and shows Harvest currency next to Salesforce billing country. Contacts are matched by email, or by name as a weak match, and listed as in both, only in Harvest or only in Salesforce. It suggests fixes without applying them, and creates or updates nothing.

Business outcome

---

One customer is checked end to end across both systems, with every disagreement listed and the fixes left in your hands.
See Full Use Case
No items found.

ready, go

Tools for Harvest

Start with ready-made MCP tools for the Harvest. Each one gives your AI client a single, clearly defined job: get invoices or journal entries, pull a file, or create and update records. Add a tool to your PopdockAI MCP server, choose the fields it returns and who can use it, and it's ready in Claude, ChatGPT or Microsoft Copilot. Nothing is exposed that you haven't switched on.

Tool Types

Name of tool
Description
get-data
harvest-get-clients
Returns clients from Harvest. Read-only Get data tool for the Harvest connector; accepts the filters the list supports.

Ready to unlock your data?

‍

Start building tools that turn your business systems into AI superpowers

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation