The Feeds Page — Controller Guide

Accounting → Feeds is where you answer one question: is the data actually getting in? Five pipelines feed your books, and this page gives each one a tab and a status vocabulary, so you can see in a few seconds which ones are current and which are waiting on you.

Who uses it: a controller checking that the month has what it needs before closing it.

Tab	The pipeline behind it
Bank Feeds	Transactions pulled from your bank each day
Payroll	Pay runs and whether they reached the ledger
Timesheets	Labor hours by pay period
Invoices	Customer invoices mirrored from the incumbent ERP
Expenses	Employee expense reports awaiting approval and posting

This page reports. It is not where you do the work. Each tab shows you the state of a pipeline and sends you to the screen that acts on it. That separation is deliberate — a page you scan every morning should never be a page where a stray click posts something.

Part 1 — Bank Feeds

The tab opens on your connected accounts. Each one carries an Account state, which is a statement about whether Arcvue should still expect activity from it:

State	Meaning
Active	Live. Transactions are expected daily, and silence here is a problem.
Hibernating	Real, but dormant. No activity expected, so silence is not a problem.
Closed	Finished. Kept for history and nothing more.

Hibernating exists so that a quiet account cannot look like a broken feed. Without it, every dormant account would sit on the page looking overdue forever, and the ones that are genuinely stuck would be lost among them. If an account has gone quiet for a reason you already know about, set it to Hibernating — you are not hiding it, you are telling the page what to expect.

Below the accounts sits Recent transactions, the day-to-day view, with these columns:

Column	What it holds
Date	The date the bank posted it.
Counterparty / Description	Who it was with, and whatever text the bank sent.
Status	The coding state — see below.
Amount	Signed, so money out reads negative.

Each transaction carries one of four coding states:

Status	What it means
Coded	Arcvue has decided which accounts this hits. Nothing to do.
Pending coding	Waiting for a coding decision.
Pending review	Coded, but flagged for a human to confirm before it counts.
Manual	Entered by hand rather than arriving from the bank.

Part 2 — Payroll

This tab is about posting, not about pay. It answers whether each pay run reached the general ledger, and it uses its own vocabulary because "did it post" has more than two answers:

Status	What it means
No entries	The run exists and nothing has been posted from it yet.
Awaiting posting	The run has been ingested and is ready to post.
Partially posted	Some of the run reached the ledger and some did not — the state that most needs your attention.
Posted	Every line reached the ledger.
Complete	The run is posted and fully accounted for, with nothing left in an unresolved bucket.
Pending mapping	Something in the run points at a pay code or account Arcvue cannot resolve yet.
Suspense	Posted, but parked in a holding account because the correct destination is not yet known.

Partially posted is the one to chase. A run that has not posted at all is obvious and a run that posted cleanly is fine. A half-posted run makes the books look plausible while being wrong by exactly the part that did not land — the totals move, so nothing looks empty.

Pending mapping and Suspense are different problems and the fix is different. Pending mapping means Arcvue has not booked it and is waiting for you to say where it goes. Suspense means Arcvue has booked it, deliberately, to a holding account so the ledger stays balanced while the question is open. A Suspense balance is a to-do list with a dollar amount attached, and it should be empty before you close.

The run list carries a Total column for the run's value.

Part 3 — Timesheets

One row per pay period:

Column	What it holds
Period	The pay period.
Status	Whether the period's labor has been posted.
Employees	How many people reported time in it.
Postings	How many ledger postings the period produced.
Hours	Total hours reported.
Labor $	The dollar value of that labor.

Status here has two values worth knowing: Pending, meaning the period's labor has not been posted yet, and Suspense, carrying the same meaning as on the Payroll tab — booked to a holding account while a destination is resolved.

Read Employees against Postings. They answer different questions — how many people reported time, and how many ledger entries that produced — and a period with employees and no postings is labor that has been reported and not yet booked. That is a real gap in the month, and it is invisible if you only look at Hours.

Part 4 — Invoices

This tab shows invoices mirrored from the incumbent ERP, not invoices Arcvue produced. The summary above the table says so directly: alongside the count of invoices in the last twelve months and the total billed, the third statistic names the Source as the ERP mirror. It is a window onto the system of record during the parallel run — a way to confirm that what the incumbent billed is visible here — and it is not your invoice register.

The window is the last twelve months, so an older invoice is absent because of the window and not because it is missing.

The mirror stops advancing at cutover, so in time this tab drains. It says so rather than reading a bare zero: the Source statistic reads ERP mirror · through the last date it recorded an invoice, and an empty window names that date and tells you that invoices billed from Arcvue live on the Invoices screen.

Column	What it holds
Invoice #	The invoice number as the ERP issued it.
Date	Invoice date.
Project	Project code, with the project title beneath it.
Customer	The billed customer.
Contract	The contract number the invoice was billed under.
Due	Due date.
Status	The status the ERP carries, passed through as-is.
Amount	The invoice amount.

A voided invoice stays in the list, dimmed, and badged voided. It is not removed. That is deliberate — an invoice that disappears is indistinguishable from one that was never issued, and during a parallel run the fact that something was voided is exactly what you are trying to see. Read the badge before reconciling a total against a count.

Part 5 — Expenses

Employee expense reports, one row each:

Column	What it holds
Date	The report date.
Submitter	Who submitted it.
Description	Whatever they wrote.
Status	Where it is in approval — below.
Total	The report total.

Draft → Submitted → Approved or Rejected → Posted. Only Posted has reached the ledger; an Approved report is a decision, not an entry.

Clicking a row opens the readiness detail for that report, which is where receipts and their extracted amounts are checked.

When the tab is empty it says so and tells you why — reports arrive from the mobile app and from operator submissions, and it links you to the full expenses screen rather than leaving you on a blank panel. That message appears only when the reports actually loaded; a load that failed says it failed instead.

Part 6 — Reading a status you have seen before

Two names appear on more than one tab, and they do not mean two different things:

• Posted always means it reached the general ledger. What differs is the subject — a pay run on the Payroll tab, an expense report on Expenses.
• Suspense always means booked to a holding account on purpose, pending a decision. It is never an error state and never a silent one.

Status columns share the name Status across four tabs and hold four different vocabularies. Read the tab you are on before reading the badge.

Posting a feed batch to the ledger

Post to GL writes a payroll run to the general ledger and reads Posting… while it works. It appears only on a run that still owes a posting:

Status on the run	Button?
Awaiting posting · Partially posted · Pending mapping	yes
Complete · Posted · No entries	no

A run with no button is almost always already done — not stuck. Complete does not mean "finished posting from here"; it means nothing is owed on that run at all, because whatever was not posted here was already booked by the timecard rail or the employer-cost feed. Reading a missing button as unfinished work is how a run gets posted twice or escalated for nothing.

Pending mapping still posts. It carries the button because the run can go to the ledger with some lines held back, and the success message names how many still need a pay-code mapping.

Part 7 — When something looks wrong

What you see	What it usually is
An account shows no recent activity	Check its Account state first — a Hibernating account is quiet by design.
A pay run sits at Partially posted	Part of the run failed to post. This is the one to chase before closing.
A Suspense balance will not clear	Something needs a destination decision; the amount is booked and waiting, not lost.
A period has Employees but zero Postings	Time was reported and never booked. A real gap in the month.
An invoice is missing	The tab shows the last twelve months from the ERP mirror only, and the mirror stops at cutover — invoices billed from Arcvue are on the Invoices screen.
A tab says it could not load	The request failed. That is not a statement that there is nothing to show; reload, and if it keeps happening the server is not answering.
A total does not match the row count	Look for dimmed rows badged voided — they stay in the list.

Related

• Bank Feeds — connecting and mapping an account, and how the feed itself works day to day.
• Payroll Pay Codes — how a pay code resolves to an account, which is what Pending mapping is waiting on.
• Timecard Ingestion and Timekeeping & Billing — where the hours on the Timesheets tab come from.
• Expenses — the full expense workflow behind the Expenses tab.
• Flightdeck — the health view of whether your books are being fed at all.