That's great! You shouldn't need to update the Macro unless something changes about the underlying data, which would break everything anyway (I'm not sure what else you may be asking with regards to updating the macro).
Here's some a good article on Batch Macro's: https://knowledge.alteryx.com/index/s/article/Getting-Started-with-Batch-Macros-1583461640393
Here's a helpful video as well: https://www.youtube.com/watch?v=NNH_K5U5r78
Trying to explain as simply as possible: A batch macro allows you to perform certain actions on chunks of data instead of running the whole data in one pass. Imagine a pre-check and standard line through airport security (they both get you to your gate, but each line may have different policies and requirements like whether you need to take off your shoes).
In your case, we care less about doing different things for each batch, and more about "batching" the data to begin with. Essentially this case just uses the first half of what a batch macro can do, but that's all you need.
Each batch is comprised of all rows with the same DC Amount, Business Area, and Profit Center. From there, a filter divides the batch into credits and debits, which are each labeled with separate RecordID's and then Union'd back together (the trick is that we can now associate matching credits and debits based on this RecordID)
Example where batch has five records:
| Debit RecordID | Credit RecordID |
| 1 | 1 |
| 2 | 2 |
| 3 | |
^ Based on the table above we now have a way to know not to delete Debit RecordID = 3, since no corresponding Credit exists.
Hopefully this was not too confusing, but thorough enough for you to understand your workflow!
