![]() ![]() The new Component TAS gives us the rest of the needed information. The BETC replaces the part of the earlier TAS system that indicated the transaction type. The BETC indicates the type of transaction (for example, payment, collection, investment, and so on). See Attachments for further details regarding these field changes. The other two significant changes to the TAS relate to the expansion of the department/agency codes and to the fiscal year fields. Sub-level Prefixes have a unique meaning or a unique need for sub classification that is NOT based on transaction types or business events as described previously. In the GWA environment, they will report the TAS 20X1234 – without the (41) – but with a separate business event type code (BETC) of FHOTXD.Īs a result, the subclass field is being renamed to "Sub-level Prefix" and will only be used for programmatic breakdowns of the TAS for Treasury publication purposes. For example, if an agency has Funds Held Outside the Treasury, they currently report TAS (41) 20X1234. Instead of the transaction type being reported as a standard subclass on the TAS, it will be reported as a business event separate from the TAS. This means that FPAs will report a TAS, without having to report sub classification of that TAS based on explicit transaction types (such as borrowings, investments, funds held outside the Treasury). The first change is the elimination of standard subclasses. Within the TAS itself, there are three other changes to note: There are many benefits to using separate, component pieces, such as having the ability to sort, filter, and analyze based on each independent piece. Fiscal Service is adopting the Component TAS (Attachment B), in lieu of the String TAS (Attachment A). ![]() Currently, FPAs report their TAS using a string format (e.g. ![]()
0 Comments
Leave a Reply. |