Unsigned Apple agreements block submission, and nothing tells you clearly

If Apple is refusing to let you submit, sell, or create an in-app purchase, check your agreements before you touch anything technical. An agreement that has not been accepted, a tax form left half finished, or banking details that never got entered will block you, and the error you see rarely says the word "agreement".

In App Store Connect this lives under Business, which was called Agreements, Tax, and Banking for years and is still referred to that way in most instructions you will find.

The three things, and they are separate

People treat this as one task. It is three, and Apple will show you as incomplete until all three are done.

1. The agreement itself is accepted. Enrolling in the Apple Developer Program covers free distribution. Anything involving money needs the paid apps agreement accepted on top.
2. Tax forms are complete. Region by region. The US form is the one everyone hits first, and there are separate forms for other territories depending on where you are selling and where you are based.
3. Banking details are entered and accepted. The legal entity name on the bank account has to match the legal entity on the developer account. A mismatch here fails quietly and takes days to sort out.

All three green, or Apple treats you as not ready to sell.

Who can actually do it

Only the Account Holder can accept agreements, or a user Apple has given the legal role to. An Admin cannot. An App Manager definitely cannot.

This matters more than it sounds, because the Account Holder on a small team is often whoever set the account up two years ago and has since left, or the founder who does not read the developer emails. The person hitting the error is almost never the person who can clear it.

Find out who your Account Holder is before you need them. It is in Users and Access.

What gets blocked, and what does not

Not everything needs the paid agreement, and it is worth knowing which side of the line you are on.

Blocked without the paid agreement:

• Creating or submitting in-app purchases and subscriptions
• Setting a non-zero price on an app
• Submitting an app that has paid content configured
• Receiving any money, obviously

Not blocked:

• A genuinely free app with no in-app purchases at all. The free distribution terms accepted at enrolment are enough.
• Uploading builds and running TestFlight, in most cases. TestFlight distribution is not a sale.
• Editing metadata and screenshots.

So if you are shipping a free app with no monetisation and something is blocking submission, agreements are probably not your problem. Look at export compliance, a missing build, or an incomplete age rating instead.

The trap: agreements get re-issued

This is the one that catches accounts that have been fine for years.

When Apple updates its terms, existing agreements move to a state where they need reviewing and accepting again. Until somebody does that, the account behaves as though it has no paid agreement. Nothing breaks loudly. Submissions that worked last month start failing, subscription creation refuses, and the developer looking at it has no reason to suspect a legal document.

Apple emails the Account Holder when this happens. Those emails go to one address, they look like boilerplate, and they get ignored.

If a previously working pipeline has started failing on anything money-related and nothing on your side changed, open Business and look for a banner asking you to review updated agreements. It is a five-minute fix and a two-day investigation if you look everywhere else first.

What the errors look like

Apple is not consistent here, which is why this page exists. Depending on where you hit it you may see:

• A banner in App Store Connect telling you agreements need to be reviewed
• The submit button simply not available, with no explanation attached to it
• An in-app purchase creation form that refuses to save
• An API error mentioning an agreement or a contract, sometimes phrased around "paid applications"
• Nothing at all, and a subscription product that never becomes available to sell

The API errors are the most useful because they say the word. The console is the least useful because it often just declines to offer you the action.

Fixing it, in order

1. Open App Store Connect and go to Business.
2. Look at the agreement list. Anything not showing as active is your blocker. Accept it, as the Account Holder.
3. Complete the tax forms for every region you intend to sell in. Start with your own and the US.
4. Enter banking details. Check the legal entity name character for character against the developer account's legal entity.
5. Wait. Apple's side takes time to process, and the status will not flip the instant you press save. Do not start changing other settings while you wait.
6. Retry the thing that failed.

Apple does not publish how long step 5 takes, and it varies with what needed verifying. Treat it as hours to days rather than minutes, and do not schedule a launch against it.

Do this before you need it

The whole category of problem is avoidable by doing the paperwork on day one, when there is no deadline attached to it.

If you are going to sell anything eventually, accept the paid agreement and complete the tax and banking forms during your first week, long before you have a subscription to configure or a launch date to hit. It costs an hour when nothing is urgent and it costs a launch window when something is.

AppSubmit checks for the agreement state when a subscription push fails and shows the Business page and the three-part checklist rather than passing Apple's error through, because the error almost never names the document. Doing it by hand is the same five steps above.