Hello – we’ve noticed our batch posting report numbers skip sequence. We’ve theorized that it’s related to Web batches. If a posting contains a Web batch, the posting report number that follows adds 10 to the number. Example: Dev posting Monday – posting report #14090. Ticket Office Posting Tuesday containing a Web batch – report #14091. Dev posting later that day – report #14101 (skips 10).
I saw another forum entry from 2010 that mentioned if users don’t complete a posting, that could cause unused numbers, and skipping. But this seems to be consistent with skipping 10 following a Web posting. Our Finance dept is concerned that something is ‘missing’. Is this by design? Anyone know?
Thanks,
…Dave
Ryan explained how this works, but to your point about Finance department concerns, I would make sure they understand that post numbers are not what they should be auditing--they will always be generated in sequence (thought not always used) but postings can be backdated such that your posting numbers may not actually end up in chronological order. One way for Finance to verify they are getting all of the relevant posting numbers is to run a GL Summary Report for the posting date range in question. In Detail mode, there will be a line (for each relevant GL) for every posting number that occurred within that date range.