Split in anticipated payments

If you decide to anticipate charges that have split applied, it will be necessary to observe some rules for using both features together.

Anticipation changes the final net amount to be received for the charge, as it considers Asaas fees and the anticipation fees themselves. Therefore, the amount available for split may be different from the original charge amount.

When to use

Use this page when your integration or operation needs to understand how split behaves in anticipated charges.

Some common scenarios include:

• anticipating a charge that has split configured;
• validating whether the fixed split amount is compatible with the net amount after anticipation;
• understanding how percentage splits are calculated in anticipated charges;
• avoiding failures when requesting anticipation of charges with split;
• guiding financial reconciliation between the anticipated amount and the amount transferred by split;
• reviewing transfer rules before anticipating installment charges or future receivables.

How it works

When a charge with split is anticipated, Asaas calculates the final amount to be credited after anticipation.

This final amount, already net of applicable fees, is used as a reference to validate or calculate the splits linked to the charge.

General flow:

Charge is created with split
↓
Charge becomes eligible for anticipation
↓
Anticipation request is made
↓
Asaas calculates the net amount after fees
↓
Asaas validates the split rules
↓
Split is applied according to the configured fixed amount or percentage
↓
Amounts are reflected according to the financial processing of the anticipation

Important concepts

Before anticipating charges with split, consider the following concepts:

Split in fixed amounts

In the anticipation of charges with split in fixed amounts, when defining the split amounts, it is necessary to observe that the maximum amount to be applied as split will be the net charge amount after deducting:

• Asaas fees;
• anticipation fees.

If the configured split amount exceeds the final amount to be received after anticipation, it will not be possible to proceed with the anticipation request in Asaas.

Fixed amount split example

Imagine a charge with the following conditions:

Gross charge amount: R$ 100.00
Net amount after Asaas fees and anticipation: R$ 90.00
Configured fixed split: R$ 95.00

In this scenario, the configured fixed split is greater than the final net amount available after anticipation.

Result:

Amount available after anticipation: R$ 90.00
Requested split: R$ 95.00
Result: anticipation will not be able to proceed

For anticipation to be possible, the fixed split amount must be less than or equal to the final net amount available after fees.

Split in percentage amounts

In the anticipation of charges with percentage splits, Asaas calculates the amount to be applied as split based on the final net amount that will be received after anticipation.

In other words, the final already anticipated credit amount will be the basis for calculating the percentage.

For example, if there is a 100% split configured in an anticipated charge, the entire amount received after the anticipation credit will be applied as split following the percentage rule.

Percentage split example

Imagine a charge with the following conditions:

Gross charge amount: R$ 100.00
Net amount after Asaas fees and anticipation: R$ 90.00
Configured percentage split: 50%

In this case, the percentage will be calculated over the final net amount after anticipation.

Result:

Split calculation base: R$ 90.00
Split percentage: 50%
Amount applied as split: R$ 45.00

If the configured percentage were 100%, the amount applied as split would be R$ 90.00.

Difference between fixed and percentage split in anticipated charges

Important rules

When using split in anticipated charges, consider the following rules:

• the split must be configured in the charge;
• the charge must be eligible for anticipation;
• anticipation considers the final net amount after fees;
• fixed splits cannot exceed the final net amount available after anticipation;
• percentage splits are calculated over the final net amount after anticipation;
• the gross charge amount should not be used as the basis to validate transfers;
• Asaas fees and anticipation fees reduce the amount available for split;
• if the split rule is incompatible with the final amount available, the anticipation may be refused;
• reconciliation must consider the amount effectively anticipated and the amounts applied as split.

Important behaviors

When anticipating charges with split, consider that:

• anticipation may change the calculation base available for split;
• the split is not calculated over the gross charge amount;
• the final net amount may be lower than the expected net amount without anticipation;
• fixed splits require validation of sufficient net balance;
• percentage splits adjust proportionally to the final net amount;
• the anticipation request may not proceed if the fixed split exceeds the available amount;
• financial reports must consider the effect of anticipation on the split;
• divergences may occur if the source system calculates the split based on the gross charge amount.

Operational impacts

The combination of split and anticipation can directly impact the financial reconciliation of the operation.

Some important impacts:

• the amount transferred by split may be lower than originally expected;
• fixed splits may prevent anticipation if they exceed the final net amount;
• percentage splits follow the reduction of the net amount caused by anticipation;
• internal reports need to differentiate gross amount, net amount, and anticipated net amount;
• commission, transfer, or marketplace rules must consider the anticipation discount;
• external systems should not assume that the split will be calculated over the gross amount;
• reconciliation divergences may occur if the integration does not consider fees and anticipation;
• financial teams must be aware that anticipating a charge can change the amount available for transfer.

Best practices

For a safer operation, it is recommended to:

• validate the estimated net amount before requesting anticipation;
• avoid configuring fixed splits close to the gross charge amount;
• use percentage split when the business rule allows proportional variation;
• consider Asaas fees and anticipation fees in internal transfer rules;
• internally record the gross amount, net amount, and net amount after anticipation;
• review split rules before anticipating high-value charges;
• test the flow in Sandbox before using it in Production;
• align with the financial area how anticipated amounts will be reconciled;
• not treat the gross charge amount as the amount available for split;
• consult the charge and split data after processing.

Common errors and questions

Checklist before anticipating charges with split

Before requesting anticipation, validate:

• whether the charge has split configured;
• whether the charge is eligible for anticipation;
• whether the split is fixed or percentage-based;
• whether the fixed split amount does not exceed the net amount after anticipation;
• whether the percentage will be applied over the final anticipated net amount;
• whether the internal system considers fees and anticipation in the calculation;
• whether the financial area is aware of the expected final amount;
• whether reconciliation differentiates gross, net, and anticipated amounts;
• whether the flow was tested in Sandbox, when applicable.

Related content

See also:

• Payment Split;
• Split in one-time charges;
• Split in installment plans;
• Split in subscriptions;
• Create charge with split;
• Retrieve split values;
• Receivables anticipation;
• Consult charge;
• Webhooks for charges.