This view exposes the rows in TFMatching that represent matching between fees ledger postings
Type = Base view suitable for advanced end user use
ClientObjectType | The object type of the client object that the account is for |
ClientInternalId | The internal id of the client object that the account is for |
Year | The year part of the fees period |
Period | The fees period number within the year |
Matching | Unique matching number within period |
WhoMatched | The internal identifier of the staff member who did the matching action |
WhenMatched | When the matching action was done |
Posting1Year | This, and the next two columns, reference the first posting that is matched (as year, period and posting number). |
Posting1Period | See Posting1Year |
Posting1 | See Posting1Year |
AmountForPosting1 | The amount to be added to the matched amount on posting 1 as a result of this matching action |
Posting2Year | This, and the next two columns, reference the SECOND posting that is matched (as year, period and posting number). |
Posting2Period | See Posting2Year |
Posting2 | See Posting2Year |
AmountForPosting2 | The amount to be added to the matched amount on posting 2 as a result of this matching action |
MatchMethod | 'A' for automatic, 'M' for manual |
Reference | Any reference associated with the matching (e.g. a VAT reference) |
VATAlreadyAccounted | If the matching is to a receipt this property is 'Y' if VAT has already been accounted on the receipt |