Overview/Roles/Operations and finance

Operations and finance

The middle of the business. Operations makes a new client safe to work for; finance makes sure the money is real before work begins and stays accurate afterwards. Together they are the reason production can trust its own inputs.

Two related roles, one purpose

Operations and finance are shown separately in Slate because they answer different daily questions. Operations asks “is this client ready, and what is missing?” Finance asks “what is invoiced, approved, and actually collected?” They meet at one point, and that point is the most important rule in the business.

The work-unlock rule No client work begins before the initial 50% payment is received and recorded. The gate opens on the accountant's confirmation — not on the money merely being seen in a bank account. This is the control that keeps the agency from financing its clients.

Part 1 — Operations: activating a client

When a deal is won, an Activation Case is created. It is a checklist with owners, due dates, required evidence, and completion conditions — not a reminder to “sort the paperwork”.

The six activation steps

  1. Proposal sent

    Scope, deliverables, pricing, and payment terms confirmed with the client. This is the record operations works from, so the client is set up the way they were sold to.

  2. Contract and documents

    Signed service agreement, Trade License, and TRN/VAT certificate collected. Missing items are listed explicitly so chasing is specific rather than vague.

  3. Invoice and payment

    The 50% invoice is prepared, the Sales Chief approves it, it is sent, payment is received, and a receipt is issued. Every one of those is a separate recorded step.

  4. Onboarding information

    Brand assets, social accounts, and credentials. Credentials go into the vault — never WhatsApp, never a chat message, never a note.

  5. Upload to Slate

    The full client profile must be on Slate within 24 hours of payment. Until it is, the client is not a single source of truth and production is working blind.

  6. Handover

    Payment recorded plus a complete profile equals handover to Content Operations. Content Operations accepts or returns it with a missing item.

The operational record — what makes a client “on Slate”

Step five is the one that is easy to tick while leaving the real work undone. Uploading a client means capturing the operational record: the facts the rest of the system reads in order to do its job at all.

Part of the recordWhy it has to be there
Identity and billing detailsContact, TRN, and billing address, so a tax invoice is issued correctly rather than completed from memory.
The agreementWhat the client is contracted to receive. Without it, nothing in the system can say what they should get and progress cannot be measured.
StrategyPositioning, audience, pillars, tone, platforms, and the learnings carried forward from performance. The running narrative, as opposed to this month's plan.
Platform accessCredentials in the vault, never in chat.

The client page shows these as a short checklist with a count, so an incomplete record is visible rather than discovered three weeks later when someone asks why the client's report looks wrong.

You do not have to type the deliverables in from scratch Slate can read what you already captured — the client notes, the strategy, the accepted proposal's scope — and propose the agreement lines for you, showing the exact phrase each number was read from so you can check it. It proposes; you confirm. Nothing reaches the client's record until a person accepts it, and the reading works whether or not the AI service is available that day.

The agreement: what the client is contracted to receive

The client page has a Deliverables tab holding two things: the agreed lines, and the live progress against them.

Each line names a deliverable, a quantity, and a cadence — every month, every week, every quarter, or once. Deliverables are not only videos: reels, stories, posts, photos, design, SEO work, and reports are all first-class lines, because a client who buys eight stories a month should see eight stories.

You seeIt means
AgreedHow many units this line owes for the period, taken from the agreement rather than typed in.
DeliveredHow many produced items on that line have reached an approved or posted state.
In productionProduced but not yet delivered — the work currently moving.
RemainingAgreed minus delivered. This is the number that matters at month end.
Two things the numbers will tell you honestly If a client has no agreement recorded, the page says so rather than showing a misleading zero. And if work has been produced that is not linked to any line, it is listed separately as unattributed so you can attach it in one tap — it is never quietly folded into a line it may not belong to.
Changing a commitment supersedes it, it does not overwrite it If a client upgrades mid-contract, the existing line is ended on the day of the change and a new one opens. Nothing is deleted, so “what did we agree in March?” stays answerable and an invoice already raised on the old terms keeps its basis. The same applies if you end a line entirely.

Watch the readiness banner

The client record shows one banner rather than making you inspect six things. It reads as one of four states:

BannerMeaningYour action
Blocked by paymentThe gate has not opened. No work may be scheduled.Chase the invoice. Do not proceed on promise.
6 items missingPayment is in, but the checklist is incomplete.Work the list. Each item names its owner.
Ready for Content OpsEverything required is present.Hand over.
Handover acceptedContent Operations owns it now.Nothing. Move to the next activation.

The document chaser

Missing documents generate a single consolidated, polite request rather than repeated nagging, and the system will not send more than one chase within the configured interval. This protects the client relationship as much as it protects your time.

The chasing is automatic. Once payment is confirmed and the checklist is still incomplete, Slate raises one consolidated request naming the outstanding items — not one message per document — and will not repeat it inside the interval. You do not have to remember to chase; you only have to act on what is listed.

The credentials vault

Client logins are the most abused data in an agency. Slate stores them properly and makes the alternative unnecessary.

PropertyHow it behaves
StorageEncrypted, with the value never visible in lists, exports, or file names.
What is recordedThe service or account, the client, the access scope, and any expiry or rotation date.
RevealRestricted by role, and every reveal is logged with who viewed it and when.
RotationSlate watches rotation dates and reminds the team before a credential expires rather than after access fails — one consolidated reminder, not one per credential.
ExportValues never leave in an export. Only the record metadata travels.

Part 2 — Finance: invoices, payments, and VAT

Finance in Slate follows the invoice's real life rather than a single status field. Understanding this sequence is the key to everything else on the finance screens.

The invoice lifecycle

Draft→ Awaiting Sales Chief approval→ Approved to send→ Sent
Part-paid→ Paid / Failed / Overdue

Sending and marking paid are separate permissions with separate audit events. That separation is deliberate: it means no single person can both authorise a payment claim and confirm it.

Invoicing on delivery, not on the calendar

Slate can raise the next invoice from a client's actual delivery progress rather than from a date. Which rule applies is a per-client setting, because clients are sold differently:

RuleThe invoice is raised when…
Share of delivery…an agreed percentage of the month's deliverables has been delivered.
Specific count…a set number of a particular deliverable has been delivered.
On cycle close…everything agreed for the period has been delivered — the balance against a 50% deposit.
Manual…never automatically. Slate tells finance the threshold has been met, and a person raises it.
Automation never sends anything to a client An automatically raised invoice is a draft, and it still has to pass Sales Chief approval before it can be sent — exactly like one you raise by hand. If a rule has no amount set against it, Slate notifies finance instead of inventing a zero-value document.

Because the trigger reads the same delivery numbers the client sees in their portal, a client can never be invoiced on a figure that disagrees with what they were told. And a rule that is missing the detail its type needs is treated as no rule at all, rather than quietly behaving like a manual one.

Confirming a payment — the two-step reality

Your real-world flow involves two people, and Slate mirrors it exactly rather than pretending it is one action.

  1. The bank-access holder supplies proof

    Whoever can see the bank account attaches the inbound transfer evidence — a screenshot, a file, or the bank reference — against the invoice. This identifies evidence providers separately from accountants.

  2. The accountant marks the invoice paid

    Restricted to the Accountant role, and it requires the payment proof to already be attached. The system will not let you mark an invoice paid without evidence on the record — the button is unavailable, and the server refuses it regardless.

  3. The receipt is issued automatically

    Marking paid generates the receipt record, which can be sent to the client as a proper document.

  4. The work-unlock gate fires

    The gate opens on the accountant's action — not on the screenshot upload. Seeing money arrive is not the same as confirming it has been reconciled.

Why this two-step design is worth the extra click If the gate opened when someone glimpsed a bank notification, an unconfirmed or misattributed transfer could start a month of work. Requiring the accountant's confirmation against attached evidence is the difference between a rule and a hope.

What the finance screens cover

ScreenWhat you do there
InvoicesRaise, approve, send, and settle invoices, with VAT breakdown and partial-payment state visible.
PaymentsRecord incoming payments, allocate them to one or more invoices, and handle partial and multi-invoice cases.
ReceiptsIssue, view, and send receipts, each numbered sequentially and downloadable as a document.
ExpensesRecord and categorise spend, mark bills paid, and void with a reason.
Credit notesIssue credits and apply them against balances, with VAT handled correctly.
VATSee the live VAT position, validate it, file the period, and lock it.
ReportsProfit and loss, cash position, receivables and payables ageing, and client balances — exportable.
Client › DeliverablesThe agreement, its live progress, the invoicing rule, and any produced work still waiting to be attributed.

Rules that protect the books

Money freezes after payment

Once an invoice has been paid against, its totals are frozen. You cannot quietly edit a settled invoice and leave the ledger disagreeing with itself.

Totals must reconcile

The server rejects any invoice whose totals do not add up from the shared money rules. Arithmetic errors are refused rather than saved.

Receipts are gap-free

Receipt numbers run in an unbroken sequence, so a missing number is evidence of a problem rather than an accident.

Voiding reverses everything

Voiding a payment reverses its allocations and restores the invoice state. Nothing is deleted, so history remains explainable.

Overpayment is refused

Allocating more than an invoice's outstanding balance is rejected. Surplus should be a credit note, not a loose allocation.

Filed periods are locked

Once a VAT period is filed, transactions in that period are blocked from change. Unlocking requires Owner or Admin and a recorded reason.

Filing VAT

  1. Check the live position

    The VAT screen shows output tax, input tax, and the net position for the current period as it stands.

  2. Validate

    Validation checks the period's records and links to anything that looks wrong, so errors are found before filing rather than after.

  3. File and lock

    Filing captures a snapshot and locks the period. The snapshot is what the return was based on, preserved even if later records change.

  4. Unlock only if genuinely required

    Unlocking is audited and restricted. It is a correction mechanism, not a convenience.

Your daily rhythm

Operations

  • Work activation cases to their 24-hour deadline.
  • Chase missing documents through the consolidated chaser rather than individually.
  • Confirm client profiles are complete before Content Operations is asked to accept them.
  • Verify no credential has been sent outside the vault.

Finance

  • Clear invoices awaiting approval.
  • Process payment proofs and mark paid against evidence.
  • Review overdue receivables and escalate deliberately.
  • Keep expenses current so the profit picture stays honest.
Slate is the record; WhatsApp is the conversation Client conversation may still happen on WhatsApp, and it should — it is where clients are comfortable. The rule is about which one is authoritative. Slate holds the facts: the agreement, the progress, the invoices, the decisions. WhatsApp is a channel that carries those facts out to the client and brings their replies back in. Anything that changes money, scope, or dates is recorded in Slate the same working day, because the 48-hour clocks, the payment gate, and the delivery figures all read Slate and nothing else.