Has anyone experienced this issue with Field Service billing? Could stale posting records, posting batches, or a known Field Service bug cause this error?
Any suggestions on additional tables, posting records, or diagnostics to review would be appreciated.