What does the full message say, and what does it mean?
The string recorded in the Acumatica community is "At least one GraphQL error has occurred. Error: Access denied for paymentTerms field. Required access: `read_payment_terms` access scope."
Read it as two facts. Shopify’s GraphQL Admin API returned the error, so the request reached Shopify and was understood. And the refusal is about permission, not about data: the app that Acumatica authenticates as was never granted permission to read payment terms, so the field is denied regardless of what is in it.
Payment terms are how Shopify B2B expresses net terms on a company, so the practical effect is that Trade credit is the practice of shipping goods and invoicing later, typically on 30-day terms, rather than taking payment when the order is placed. It is the default in most B2B relationships. information stops flowing between the two systems while orders and products keep syncing normally. That is why it often gets noticed late.
Checked against: Acumatica community 31039: 25R1 Shopify payment sync error, read 20 August 2026
What actually causes it?
A scope grant that is older than the connector code using it. Shopify grants access scopes when an app is installed. If a later Acumatica release starts reading a field that needs a scope your installation never asked for, the existing grant does not expand on its own and every request for that field is denied.
The thread ties it to the 25R1 upgrade specifically: the connector lacked the required access scopes after the upgrade. This is the general shape of a whole family of Acumatica Shopify errors, and the family is worth recognising because they all look different and all have the same fix. "Access Denied for publicationCreate field" on Shopify Plus price list sync, "Access denied for exchangeV2s field" on refunds, and "Access denied for companyContactProfiles field. Required access: `read_customers` access scope or `read_companies` access scope" on 2025 R2 are all the same failure with a different field name.
Checked against: Acumatica community 31039, read 20 August 2026, Acumatica community 22625: Access Denied for publicationCreate field, Acumatica community 35087: companyContactProfiles access scope on 2025 R2
How do you clear it?
It depends entirely on whether you connected Shopify through the public Acumatica app or through a custom app you created in your own Shopify admin. Find that out first, because the two fixes have nothing in common.
Public Acumatica ERP app: reinstall it. The accepted answer in the thread is to reinstall "to ensure you have the latest version, which includes all the required access scopes", and the original poster confirmed "we are using public app, and reinstalling worked for us".
Custom app: check your configured access scopes against Acumatica’s documentation for the connector and add the missing one, or recreate the app if the scope list cannot be amended in place.
Before you reinstall, record your store settings and entity mappings. A follow-up question in the thread asked whether reinstalling means re-entering all Shopify store settings and mappings into Acumatica, and it went unanswered. Assume you may have to and take the screenshots.
Re-run the failing sync and confirm the payment terms land on the company record, not just that the error stopped appearing.
Checked against: Acumatica community 31039, accepted answer and confirmation, read 20 August 2026
What if reinstalling does not clear it?
Check your Shopify plan against the entities you have switched on. This is the trap, and it caught a user on 2025 R2 with the companyContactProfiles version of the same error: they had the Company and Customer Location entities enabled while running on Grow and Advanced plans. Deactivating those entities and resyncing resolved it, because the B2B objects those entities need are not available to that plan in the way the connector expects.
So the two causes look identical in the error text and are opposites in the fix. A missing scope on a plan that supports the feature is fixed by reinstalling. A supported scope on a plan that does not carry the feature is fixed by turning the entity off, and no amount of reinstalling will touch it.
This observation comes from Acumatica 2025 R1 for the paymentTerms field and 2025 R2 for companyContactProfiles, both read on 20 August 2026. Shopify changed which B2B features are available below Plus on 2 April 2026, so the plan-related half of this answer is newer than a lot of the advice you will find, and it should be re-checked as both products move.
Checked against: Acumatica community 35087: entities enabled on a non-Plus plan, read 20 August 2026, Shopify changelog: key B2B features on non-Plus plans, 2 April 2026
Common questions
- How do I fix “Access denied for paymentTerms field” on Acumatica 25R1?
- If you connect Shopify through the public Acumatica ERP app, reinstall it, which is the fix the community thread’s original poster confirmed worked. If you use a custom app, add the read_payment_terms access scope or recreate the app. Record your store settings and entity mappings before reinstalling, because whether they survive was asked in the thread and never answered.
- Why do these Shopify access scope errors appear after an Acumatica upgrade?
- Shopify grants access scopes at install time and does not expand them later. When a new Acumatica release starts reading a field that needs a scope your installation never requested, every request for that field is denied. The same pattern produces the publicationCreate, exchangeV2s and companyContactProfiles versions of this error.
- Could our Shopify plan be causing this rather than the scopes?
- Yes, and it is the case reinstalling will not fix. On Acumatica 2025 R2 a user hitting the companyContactProfiles version of this error had the Company and Customer Location entities enabled on Grow and Advanced plans, and deactivating those entities resolved it. Check which B2B entities you have switched on against what your Shopify plan actually carries.
Last updated 2026-08-20. Facts on this page last checked against source 2026-08-20.