Hi Benard Muinde your question could mean a few different things but I'll take a guess that your problem is:

1. You have setup A/R Invoice integration between a membership or billing system and Sage 300 via the Web API.
2. When the integration runs and there is only a single invoice to push into Sage 300, the Web API creates a new A/R invoice batch with 1 entry in it.
3. You do not post the invoice batch, leaving it open.
4. Later, the integration runs again and another invoice is pushed into Sage 300 via the Web API.
5. Instead of the second invoice being placed as entry 2 in the first unposted batch, a second invoice batch is created with 1 entry.
6. You now have two open A/R invoice batches both with 1 entry.
7. You're worried this will make a long mess of your A/R Invoice Batch Listing
8. You want all A/R invoices created by the Web API integration to go into the next open batch until you post it.

Is this correct as it was a common question long before the Web API when integration was done with Sage 300 VB Macros and other methods?  Awaiting your clarification. Cheers.

Hi Benard Muinde your question could mean a few different things but I'll take a guess that your problem is:

1. You have setup A/R Invoice integration between a membership or billing system and Sage 300 via the Web API.
2. When the integration runs and there is only a single invoice to push into Sage 300, the Web API creates a new A/R invoice batch with 1 entry in it.
3. You do not post the invoice batch, leaving it open.
4. Later, the integration runs again and another invoice is pushed into Sage 300 via the Web API.
5. Instead of the second invoice being placed as entry 2 in the first unposted batch, a second invoice batch is created with 1 entry.
6. You now have two open A/R invoice batches both with 1 entry.
7. You're worried this will make a long mess of your A/R Invoice Batch Listing
8. You want all A/R invoices created by the Web API integration to go into the next open batch until you post it.

Is this correct as it was a common question long before the Web API when integration was done with Sage 300 VB Macros and other methods?  Awaiting your clarification. Cheers.

Hi Tim - Accsys Consulting  you got it right. That's the issue I'm dealing with. I want all A/R invoices created by the web API integration to go to the same open batch until posted, instead of creating a new batch every time an invoice is pushed.