Per-file pay explained: how to judge an offer

Questions to ask about any per-file pay offer, how to convert it to an hourly equivalent from your own time records, and where it can go wrong.

US rule; elsewhere, check your own regulator · Updated November 20, 2026

Per-file pay means a set price for each file of a defined type. It is common wherever one party sends many similar files to another. This guide is neutral. It does not state any rate and it does not describe any one buyer's terms. It gives you the questions and the arithmetic to judge any offer yourself.

Country-neutral: the method. US rule: the fee limits in the last section. Check your own regulator for fee rules elsewhere.

What per-file pay really is

It is a fixed fee with a standard unit. You are paid for the file, not for the hours. That means the number that matters to you is the hourly equivalent: price divided by the hours the file takes you, from receipt to the last review note answered.

The model has real strengths. You know the price before you start. Your pay rises when you get faster. The buyer can budget by volume. The risk is variation: files are rarely identical, and the average hides the spread.

Ten questions to ask before you accept

Put these to the buyer, and get the answers in writing in the agreement.

  • What is a file? Define it by content: which statements, which period, which schedules, which supporting documents.
  • What are the limits? State size or complexity limits, such as number of entities, accounts or transactions, and say what happens when a file goes over.
  • What does the price cover? List the tasks: the work itself, answering review notes, a final read, any updates after delivery.
  • What counts as rework? Say who pays when the buyer asks for changes caused by information that arrived late, and who pays when the changes come from your own errors.
  • Do I choose which files I take? If files are offered to you and you may decline, say so. If you must accept what comes, the spread of file sizes is your risk.
  • Is volume promised? If not, you should not plan your calendar around a flow that is not committed.
  • When is the file counted as done? Define acceptance, so payment does not hang on open-ended review.
  • When am I paid? State the payment term and the point it starts from.
  • Is any part of the price dependent on the result of the work? If so, read the section below on contingent fees.
  • How can the price change? Set the notice period and say whether a change applies to files already started.

An offer that cannot answer these is not yet an offer; it is a conversation.

Do the hourly-equivalent test

You need your own time records. If you have none, time the first files you do under any new arrangement and treat the first set as a trial.

  • Take a sample of files of the type offered, as many as you can.
  • For each, record all the hours: reading, doing the work, queries to the buyer, review notes, rework.
  • Divide the price by the hours. Look at the average, and look at the worst case, not only the average.
  • Compare with the required rate you built using the method in the main rates guide.

Illustrative example, labelled as such, in plain units. A file is priced at 300 units. You time five files: 2.5, 3, 3, 4.5 and 5 hours. The total is 18 hours, the average is 18 / 5 = 3.6 hours, and the average equivalent rate is 300 / 3.6 = 83.3 units an hour (rounded). The best file gives 300 / 2.5 = 120 units an hour. The worst gives 300 / 5 = 60 units an hour. If your required rate is 80 units, the average clears it by a little, but two of the five files (4.5 and 5 hours, at 66.7 and 60 units an hour) fall below it. You now know what to negotiate: a size limit, a surcharge band for larger files, or the right to decline files that exceed the limit.

The per-file-to-hourly calculator on this site does the arithmetic with numbers you enter. Nothing is stored.

Where per-file offers go wrong

  • Hidden scope. The file arrives with missing records, and the price assumed complete ones.
  • Open-ended review. Review notes keep coming and each round costs hours the price did not include.
  • Averages. The price was set for an average file, and you receive the long tail.
  • Speed pressure. A short return time combined with a low price pushes you towards shortcuts. Professional standards still apply to the work, and a price that cannot support the procedures required is a problem for you and the firm that signs.
  • Unwritten changes. Terms are changed by message, and nobody records the date.

Fixing a weak offer

You can often make an offer work without raising the base price:

  • Add a complexity band: a standard price up to a stated limit and a higher price above it.
  • Cap the number of review rounds included, and price additional rounds by the hour.
  • Define late or incomplete information as a trigger for a change in price or date.
  • Keep the right to decline a file that is outside the definition.
  • Ask for payment on delivery or on a short term in place of a long one.

Where a buyer does not move, you can still accept if you can say why: new work type, relationship, a spare slot. Decide it as a business choice with the number in front of you.

Contingent pay is a different thing

A flat per-file price, set before work and paid whatever the file shows, is not a contingent fee. If any part depends on the result, such as an extra amount when a file is clean or a deduction when a position is questioned, check it. US rule: Circular 230 section 10.27 limits contingent fees for services in connection with matters before the IRS, and the AICPA Code has its own rule for members in public practice at ET 1.510.001. The contingent-fee guide in this section explains the pattern and the questions to ask. Check your own regulator elsewhere.

Frequently asked questions

Is per-file pay worse than hourly?

Not by nature. It is better for you when your files are alike and you are fast, and worse when files vary and the price assumed an average. Test it with your own records.

What is a fair price per file?

This guide does not give one. A fair price is one that clears your required rate on your own data and that both sides accept in writing.

Can I refuse a file I have already started?

Only on the terms of your agreement. That is why the definition of acceptance, rework and declined files matters before you begin.

Should rates for the same work differ by buyer?

They can. Different buyers bring different review burdens, volumes and payment terms, and those differences are a fair reason to price differently.

Does the buyer need to tell me how the price was set?

You can ask. A buyer that can describe its basis is easier to negotiate with, but it does not have to.

Sources

Last verified November 20, 2026. Sources checked by the editorial team; not yet reviewed by a named professional. General information, not legal, tax or accounting advice.

Related pages

Terms used on this page

Contingent fee

Join the CORAA CPA network waitlist

CORAA prepares audit files for US CPA firms. Network members are independent contractors who clear what the software flags, with evidence and a note, paid per file under a contractor agreement.

  • Files are offered to you; you accept or decline
  • No exclusivity: you can work for others
  • The firm reviews and signs; CORAA never does

* required