The paperwork a client’s own systems force on you

The hidden cost of a bigger client

A large customer looks like an unambiguous improvement: more work, better rates, an established payer. What is rarely priced is the administrative apparatus that comes with them, because organisations of any size do not simply buy things — they have processes for buying things, and those processes were designed for suppliers with an administration department.

For a one-person business, that apparatus lands on the same person who does the work, quotes for it and invoices for it. The hours are real and they are unbillable, and they are one of the main reasons a prestigious client can turn out to be worth less than a straightforward one.

What onboarding usually involves

Before any work happens there may be forms establishing who you are, evidence of insurance, references, bank verification, a questionnaire about how you handle information, and sometimes a requirement to register on a system that exists solely to hold supplier records.

None of it is unreasonable from their side, and collectively it can consume a day or more. It is worth knowing this before agreeing to a small first job, since the setup cost is the same whether the engagement is worth very little or a great deal. A modest trial project with a large organisation can be a genuine loss once the onboarding is counted.

The reference that decides whether you get paid

Many organisations will not pay an invoice that does not carry a purchase order number or an equivalent reference, and they will not always tell you that in advance. An invoice missing it is not queried so much as ignored, and it can sit unprocessed for weeks while you assume it is progressing normally.

So the questions to ask before starting are narrow and specific: is a reference required, who issues it, where should the invoice be sent, and what else has to appear on it. Five minutes at the beginning removes the most common cause of a payment being late for reasons that have nothing to do with anybody’s willingness to pay.

Systems that replace your own

Some clients require work to be tracked in their system, time recorded in their format, communication conducted through their platform, or invoices submitted through a portal that behaves unlike anything else you use.

The cost here is not only the time. It is that your own records now live in two places, and the client’s system is one you will lose access to when the relationship ends. Keeping your own copy of anything that matters — what was agreed, what was delivered, what was invoiced — is worth the duplication, because supplier access is usually switched off the day the work stops.

More of it is negotiable than it appears

Requirements handed down by a large organisation are presented as fixed, and a proportion of them are not. Insurance levels sometimes reflect a standard template rather than the actual risk of your work. Questionnaires designed for large suppliers occasionally have a simplified route for small ones. Payment terms are frequently negotiable in a way that nothing else in the document is.

The person to ask is usually not your contact but whoever administers the process, and the request lands better when it is specific and proportionate. Asking whether a requirement designed for a large supplier applies in the same way to a business of one is an ordinary question, and it is answered more helpfully than most people expect.

Price it, or decline it

What should not happen is absorbing all of it silently. If a client’s process adds several unbillable hours to every engagement, that is a cost of serving them, and it belongs in the rate exactly as travel or materials would.

It is also a legitimate reason to decline. A small job wrapped in a large organisation’s procurement requirements can be worth less than the same work for somebody who pays on receipt of a one-page invoice. Knowing that before agreeing is the whole point, and the only way to know is to ask what the process involves before quoting rather than after.

The consolation is that most of it is paid once. Onboarding, registration and learning the system are a fixed cost of the relationship rather than of each job, which means the arithmetic improves sharply if the work continues. That is the honest case for accepting the burden: not that it is reasonable, but that a client worth several years of work can absorb a day of setup, and a client worth one small job cannot.