A salaried employee gets a pay statement as a by-product: payroll runs, and a document falls out of the run whether or not anyone planned for it. Contractor work has no machinery behind it. You send an invoice, the client pays the invoice, and the accounting event ends there. Nobody produces a record of what the period looked like, because from the client’s side there is no period — only a bill that got settled. So the wage-style document never arrives on its own. What follows is the version you keep yourself: a freelance earnings record built from payments you have already received, one period at a time, with the fields that make it readable later.
Why keep a per-payment record at all
Most contractors already have an invoice log. It is a genuinely useful table — invoice number, date sent, amount, due date, date paid, days outstanding — and it answers one question very well: was I paid? Once every row reads “paid”, the log has nothing left to tell you. It cannot describe a period, because it is not organized around periods.
A per-period earnings record answers a different question: what did this period look like? Three things become visible the moment you keep one, and none of them show up in an invoice log. The first is volatility. Six months from now you will not remember that February was thin; you will have a feeling that the year was “up and down”, which is useless for planning anything. The second is concentration — how much of a year stands on one relationship. The third is the shape of lateness. Your invoice log tells you an invoice cleared on the 11th. A period record tells you the March figure is really February’s work plus eight days of March’s, which is the fact you need when you compare one month to the next.
That is the honest case for it, and it is entirely internal. This is where a pay stub for independent contractors stops being a curiosity and starts being a worksheet: a page in your own books that states one period’s earnings, on one basis, in one place. Where your client’s own year-end paperwork fits next to it is a separate question, and the guide on which of the three records answers which question already covers it — this page will not re-teach that comparison.
The fields worth keeping
A contractor’s record has fewer lines than an employer’s, and each one earns its place by making a later question answerable without reconstruction. The table below is the set I would keep, with the failure on the right — the specific thing that goes wrong when the field is missing, which is nearly always “I know roughly what happened and cannot say exactly”.
| Field | Why it earns its place | What breaks without it |
|---|---|---|
| Payer | The client, written as they write themselves, including the entity suffix. | You cannot sort the year by client, and two projects blur into one number. |
| Payee | Your name, or the trading name you invoice under if they differ. | Two years later you cannot tell which of your own accounts a payment touched. |
| Period start and end | The work window, not the calendar month you happened to bill in. | Every month-to-month comparison is quietly wrong at the edges. |
| Payment date | The day the money landed, kept separate from the period it covers. | Timing disappears; a slow month looks like a small month. |
| Hours or milestone | The unit of work the amount was formed from. | No one, including you, can check the arithmetic. The figure is just asserted. |
| Rate | Per hour, per day, or the fixed price for that milestone. | A change in rate mid-year becomes invisible, and so does a good negotiation. |
| Gross for the period | Hours or basis times rate, stated as one number. | The period has no total to roll up into the quarter or the year. |
| Expenses you fronted | Software, travel, materials you paid for on that job and did not bill back. | Good-looking periods that were actually thin, and nobody tells you later. |
| Amount received | What actually arrived, after anything the client held back. | Your record and your own notes disagree, and you cannot say which one is right. |
| Method | Transfer, platform payout, check. Whatever lets you find it again. | Reconciling a busy month means opening five tools to hunt one payment. |
| Invoice number | The link back to your own log, and to the client’s accounts payable. | The two records never join, so you maintain both and trust neither. |
| Notes | One line: a rush fee, a scope cut, a payment plan you agreed to. | The explanation for an odd figure is gone, and the odd figure looks like a mistake. |
Two of those lines deserve a comment. Hours or milestone plus rate is what turns a total into something checkable; the same logic that divides an annual figure into a weekly one applies here, and turning a rate into a period figure is worked through on its own page. Expenses you fronted is the line most contractor records omit, because an invoice never had it. It belongs on the earnings record precisely because the earnings record is yours and not a bill. For the vocabulary the other lines borrow — gross pay, net pay, pay period, regular rate, and reimbursement, which is the word for a fronted cost a client pays back — the 25-term payroll glossary defines each in one paragraph, and the field-by-field anatomy of a stub shows where they sit on a page.
What an earnings record is not
Three negative facts, stated plainly. It is not a form any agency issues, so no one else holds a copy of it and nothing about it is standardized. It is not a statement from whoever paid you; their statement is a different document, made by them, about their own records. And it carries no withholding line, because nothing was withheld from you — no employer ran you through payroll, so gross and the amount you received are the same figure unless a client held something back for a specific contractual reason. Keep those three in view and the record stays what it is: your own bookkeeping, in your own hand. The broader question of what a pay stub is and what it can prove is settled on its own page and is not repeated here.
Quarterly reality: the numbers that move
Here is what a quarter looks like when you write it down. The figures are illustrative and deliberately round: a freelance designer, one project per client, three months. Client A is a retainer-style relationship billing monthly; Client B is small and intermittent.
| Line | Client A | Client B | Gross for the month |
|---|---|---|---|
| January | $4,800 | — | $4,800 |
| February | $3,200 | $1,500 | $4,700 |
| March | $6,400 | $900 | $7,300 |
| Quarter | $14,400 | $2,400 | $16,800 |
| Fronted expenses: software $145, travel $380, equipment $620 | −$1,145 | ||
| Quarter after out-of-pocket costs | $15,655 |
Four readings of that table, all of which need the per-period record and none of which the invoice log supplies. The spread. $4,800, then $4,700, then $7,300 — March is about 55% above February, and the quarter is carried by it. A year made of months like this does not behave like a salary, and dividing the annual total by twelve describes it badly. Concentration. Client A is $14,400 of $16,800, roughly 86% of the quarter, with the second client contributing two small invoices. The hidden line. $1,145 left your own account to do that work, so the gross figure overstates the quarter by about 7% — it is the difference between a total that arrived and a total that was actually yours to keep.
The fourth reading is the one people skip, and it comes from the shape of those three months rather than from any cell in the table: because the months swing, the money you set aside swings too, which is the practical reason quarterly estimated payments exist at all. What you owe, when, and on what basis is not arithmetic this page should attempt — it depends on your filing situation, your state, and your costs, and it is a conversation to have with a professional rather than a number to copy off a website. Keep the periods clean and itemized, and that conversation is short. Keep them vague, and you are paying someone to reconstruct your year first.
Organizing and keeping the files
One folder per client, one sheet for the year
Folder structure by client, because that is how the work arrives and how a dispute about March is settled. Records organized by period, because that is how the year is read. Those are two different axes, so keep both: a folder per client holding that client’s invoices and payment records, plus one combined view for the year — a single sheet whose rows are periods and whose columns are clients. The combined sheet is the artifact that answers “how was the first half?”; the folders are what you open when a specific payment needs explaining.
Names that sort themselves
Name every file with an ISO date first, then the client, then what it is, so a folder of twenty documents still reads as a timeline: 2026-02-28_client-a_design-fee.pdf and 2026-02-28_client-a_inv-0414.pdf. A date written YYYY-MM-DD sorts chronologically in any file manager and in any locale, whereas “Feb 28” sorts next to January and “2/28” sorts somewhere else entirely. Putting the client in the filename matters for the same reason: the moment two files land in your downloads folder out of context, the name is the only thing that still says where they came from.
The invoice and the payment record side by side
Keep both documents for each payment, in the same folder, under the same date prefix. They are not duplicates. The invoice is what you asked for and when you asked; the payment record is what the period produced, including the parts you never billed — hours that ran over, expenses you absorbed, the date the money actually arrived. Storing one and “having the other somewhere” is how people end up with a folder of invoices and no answer about a specific February.
How long, and in which format
How long you keep any of it is your own decision, and reasonable people land in different places depending on their contracts and their accounting. The useful note here is about format, because the two obvious choices fail differently. A spreadsheet fails quietly: a cell gets overwritten, a formula range stops one row early, and the totals still look plausible while being wrong; there is no audit trail because none was ever intended. A PDF per payment fails noisily and spatially — thirty good documents in a folder you stop opening, impossible to total without retyping them. So keep the spreadsheet as the working year view and the PDFs as the per-period originals, and let the two check each other on the quarter.
Turning a paid invoice into a period record
If writing those fields out by hand is the friction that stops this from ever happening, the generator is the same act with the arithmetic done for you: you enter the client as payer, your name, the period start and end, the payment date, and hours or a fixed milestone with its rate, and gross, deductions and net update on the preview while you type. A total that does not reconcile is therefore visible before you commit to it, and what you export is a one-page PDF of that period to file next to the invoice. People looking for pay stubs for contractors usually want exactly that and nothing grander, so Generate My Pay Stub for a payment you have already received, drop it in the client’s folder, and let the habit be worth more than any single document — a self-employed pay record only accumulates when you write one every time money arrives.
Frequently asked questions
Do clients have to give me a pay stub?
A client paying an invoice is not running payroll, so there is usually no wage statement at the end of it. What exists instead is the invoice and the payment, and the picture of what the period looked like gets assembled from those two by whoever kept them — for contract work, that is you.
What is the difference between an invoice and an earnings record?
The invoice is the request. The earnings record answers what the period looked like once the money arrived, and it carries companions the invoice has no room for: the payment date, what you fronted, which client the money came from, and whether the hours behind it were billed at one rate or three.
How should the files be organized?
One folder per client with an ISO date at the front of each filename, plus a single view of the year that adds them up. The questions come in two shapes, so the filing does too: which invoice is still open, and what a quarter actually earned after the costs you carried yourself.
Is a record I keep myself enough on its own?
For your own books, keeping one is the point. What it cannot become is a statement from whoever paid you, since you wrote it. A figure confirmed by the other side has to come from the other side, and nothing you generate here changes who signed it.