Knowledge & operationsBLoc Agency Manager11 min read

Managing Translation Agency Clients, Jobs, Invoices, Purchase Orders, and Client Portals

Replace scattered spreadsheets with connected clients, jobs, invoices, purchase orders, and role-based client portals for translation agency operations.

Executive summary · 11 min read
  • Connect client, vendor, and job records first; invoices and purchase orders inherit their accuracy from that structure.
  • Generate invoices and purchase orders from operational job data and review before issuing — no re-typing, no reconciliation archaeology.
  • Review reserved versus consumed subscription usage on a fixed cadence so renewals are reports, not arguments.
  • Hosting, portal setup, data migration, and payment-provider integration are scoped separately; contract them explicitly.
Financial Governance & Encrypted Backups: In BLoc Agency Manager, issuing an invoice or purchase order generates a reviewable document without emailing it automatically, manual payment entries are staff-recorded evidence rather than bank proof, and currencies remain separate until an explicit exchange rate is entered. Always export passphrase-encrypted backups and restore only into a clean empty folder.

Boutique localization agencies rarely fail on translation quality; they leak margin through operations. The client list lives in one spreadsheet, vendor rates in another, jobs in a third, invoices are assembled by hand at month-end, and purchase orders are reconciled against statements nobody fully trusts. BLoc Agency Manager replaces that patchwork with connected client, vendor, and job records and builds commercial documents from the same operational data the team already maintains. This guide covers the workflows that matter once an agency outgrows ad-hoc files, and the boundaries that are scoped separately.

Why spreadsheet operations fail at agency scale

Spreadsheets are capable single-user ledgers and unreliable multi-user systems. The failure modes repeat from agency to agency because they follow from the format itself.

  • Identity drift. "Acme Corp", "ACME Corporation", and "Acme (EU)" occupy three rows but denote one client, so revenue per client is an estimate.
  • Status lives in inboxes. The tracker says "in progress"; the real status was decided in an email thread nobody pasted back.
  • Re-typed commercial data. Copying job lines into invoice templates introduces wrong rates and missed jobs — and the error surfaces on the client's statement, not yours.
  • PO matching is archaeology. Reconciling a client purchase order to the jobs it covers happens monthly, from memory, when someone asks.
  • Usage is invisible until renewal. Reserved versus consumed capacity is reconstructed after the fact, when the argument has already started.

None of this is a discipline problem. It is the predictable result of keeping records that depend on each other in files that do not.

Connected client, vendor, and job records

The product keeps client, vendor, and job information together instead of in separate lists. Client records hold contacts and commercial context; vendor records hold the suppliers you buy capacity from; job records reference both. Opening a job shows the client's terms and assigned vendors as context rather than as a lookup exercise, and questions such as "which jobs ran for this client with that vendor last year" become record queries with consistent answers for everyone who asks.

Connection also changes error behavior. Correct a client's legal name once and every job, invoice, and purchase order that references it inherits the correction — in a spreadsheet, the same correction must be found and applied in every file where the name appears.

What belongs in each record

Client records carry the contacts you actually communicate with, the commercial context that governs their work, and the subscription plan they consume. Vendor records carry the suppliers and freelancers you buy capacity from, so assignment is a choice between real options. Job records carry the request, the order it became, and the vendor work assigned against it — the single thread that ties a client's need to a vendor's invoice.

Shared order and job tracking

Requests, orders, and assigned work move through shared job records, so the status one person sees is the status everyone sees. The coordinator updates the job record once; clients, vendors, and colleagues read the same state instead of maintaining private copies. This removes the daily status chase across chat and email and gives a truthful queue for planning: which jobs wait on the client, which on a vendor, and which are genuinely blocked.

Shared records also make handovers survivable. When a coordinator is out, the job record carries the state, so work continues from the record rather than from memory.

Invoices and purchase orders from job data

Invoices and purchase orders are prepared and reviewed from the same operational data that records the work. The job lines are the source and the documents are projections of them, which removes the re-typing step where most billing errors begin. The same structure works in both commercial directions: what the client owes and what you owe vendors derive from one set of job records, so the two sides of the margin reconcile by construction.

Review stays human. Documents are prepared for review before issue — credits, negotiated rates, and rounding remain coordinator decisions — while completeness and arithmetic come from the records rather than from memory at month-end.

Purchase orders deserve the same respect on the vendor side. When a PO is generated from the job record and sent before work starts, the vendor's invoice can be matched against a document you issued, not against a memory of what was agreed — and month-end reconciliation becomes a check instead of an investigation.

Subscription plans and usage tracking

For teams selling or consuming subscription-based localization capacity, the product manages subscription plans and reports reserved versus consumed usage. The distinction is commercial, not cosmetic: reserved is the committed capacity; consumed is what the work actually took. Reviewing the gap on a fixed cadence turns renewals into reports, surfaces under-used plans before the client notices them, and shows where capacity was over-committed while there is still time to rebalance.

Pick the cadence to match your commercial rhythm — monthly for fast-moving accounts, per-milestone for project work — and record the review itself, so the next person can see when usage last reconciled.

Client request portal with role-based access

The client request portal gives clients a structured channel for requests and visibility into the records relevant to them, with role-based access controlling who sees what. Requests arrive as records attached to the right client instead of prose in an inbox that a coordinator must transcribe. Portal scope is configured, not assumed: which records clients see, and how the portal is set up, are agreed during configuration with your provider.

Role-based access is what makes the portal safe to open widely. A procurement contact sees the records their role needs; a project contact sees job status; nobody sees another client's pricing. Setting those roles per contact — before access is granted, not after — keeps the portal an asset during audits rather than a liability.

Import, export, and scoping boundaries

Supported records can be imported and exported when information moves between systems — legacy spreadsheet data on the way in, extracts for accounting and reporting tools on the way out. Keeping that boundary explicit is a feature: BLoc Agency Manager is the operational system of record for agency work, not a replacement for every adjacent system.

Production note: hosting, portal setup, data migration, and payment-provider integration are agreed separately; the subscription does not include a hosted service or payment-processing fees. Contract those pieces explicitly before committing a portal date to a client.

Spreadsheet versus connected records

Operational questionSpreadsheet practiceConnected records practice
Who is this client?Name variants across files; identity resolved by memoryOne client record referenced by every job and document
Where is this job?Tracker row plus an email thread holding the real statusShared job record that every stakeholder reads
What does the client owe?Job lines re-typed into an invoice templateInvoice prepared from job data and reviewed before issue
What do we owe vendors?Reconciled monthly against statementsPurchase orders derived from the same job records
How much plan capacity was used?Reconstructed at renewalReserved versus consumed usage reviewed on a cadence
How do clients submit work?Email prose transcribed by a coordinatorRole-based portal requests stored as records

Operational checklist

  1. Inventory existing spreadsheets and classify each list as client, vendor, or job data before importing anything.
  2. Agree the separately scoped items first — hosting, portal setup, data migration, payment provider — because their lead times drive the schedule.
  3. Import or enter client and vendor records and normalize names once, before any job references them.
  4. Create job records for all open work and assign vendors so in-flight state is visible to everyone.
  5. Generate the next invoice and purchase order drafts from job data and review both before issuing.
  6. Record subscription plans and review reserved versus consumed usage on a fixed cadence.
  7. Set portal roles for each client contact before granting access, so visibility matches the contract.
  8. Export records on a schedule as both a backup and the input to external reporting.

Technical FAQ

Is BLoc Agency Manager a hosted SaaS?

No. It is a local Windows application that you download and activate with a License ID and Activation code. Hosting, portal setup, data migration, and payment-provider integration are agreed separately, and the subscription does not include a hosted service or payment-processing fees.

Can clients submit requests without email chains?

Yes. The client request portal accepts requests as records with role-based access to the records relevant to each contact. Which records clients see, and how the portal is configured, are agreed during setup.

Do the invoices replace our accounting system?

No. Invoices and purchase orders are prepared and reviewed from operational job data, then issued through your existing process. Export supported records when your accounting or reporting tools need them.

How do we bring years of spreadsheet history across?

Through supported record import and export. Data migration is scoped and agreed separately, so plan it deliberately: normalize client and vendor identity first, then import jobs in chronological order so history stays coherent.

The BLoc Agency Manager tool page and the interactive walkthrough show the records and documents in context, and the request form starts the configuration conversation in writing. Related reading: cleaning contact lists and running Classic Outlook campaigns and building editable guides and style guides from project evidence.

BLoc Agency Manager · Agency operations

Ready to apply this workflow in production?

Manage clients, jobs, invoices, purchase orders and subscription requests in one connected workspace. Pricing: $15 / month or $150 / year.

← All 14 localization engineering guides