3777487 - Service Contract Migration: Billing Status Cannot Be Set to “Billed” via API for Legacy-Billed Contracts in SAP S/4HANA Cloud Public Edition

During migration, service contracts that were already fully billed in a legacy system remain active after go-live. Customer wants to update the billing status to “Billed” in SAP S/4HANA Cloud Public Edition via API or migration.

SAP S/4HANA Cloud Public Edition

1. Create/migrate a service contract using legacy contract start/end dates and total contract value.
2. Contract was already billed in the legacy system before go-live.
3. Check the migrated service contract/billing plan in SAP S/4HANA Cloud Public Edition.
4. Attempt to update the billing status to “Billed” via API or migration.
5. Billing status cannot be directly updated.

The billing status of a service contract is system-derived. It is determined from the billing plan and actual billing execution/billing request lines in SAP S/4HANA Cloud Public Edition. There is no standard migration field or API method to manually set historical billing status to “Billed” for legacy-billed contracts.

It is not possible to directly update the billing status to “Billed” via API.

Supported options are:

1. Structure the billing plan so no further billing is expected, for example by only migrating future relevant billing periods or ensuring no remaining billable value exists.
2. If historical billing/accounting recognition must be reflected, validate a controlled post-migration adjustment or billing-history reconstruction approach in a test system.
3. Review the migration template and billing plan setup before mass migration to avoid duplicate billing or unwanted catch-up effects.

Note
Preventing further billing does not mean the system will display the historical contract as “Billed”. That status is only reached through standard billing execution in SAP S/4HANA Cloud.

• Refer to: Service contracts (Help Portal)
• Refer to: Customer projects migration – handling partially/fully billed legacy objects

service contract migration, already billed, legacy billing, go-live, billing plan, avoid duplicate billing, remaining service period, SAP S/4HANA Cloud Public Edition, Public Cloud, item-level billing plan, billing status, billing request lines, catch-up billing, data migration, migration cockpit, Manage Service Contracts, Service Contract A2X API, OData API, historical contracts, legacy invoicing, billing document request (BDR), event-based revenue recognition (EBRR) , KBA , CRM-S4-SRV-CTR-2CL , S4CRM: Service Contract (Public Cloud) , Problem