تسوية البنك وتصنيف المعاملات

المتطلبات تصف قدرات يحتاجها النمط في بيئتك، مو الموردين اللي لازم تشتريهم. أي نظام يملأ متطلباً يحقّقه — وهذا اللي يخلّي الكتالوج قابلاً للنقل عبر الذيل الطويل من أدوات الشركات الصغيرة والمتوسطة.

1. bank_transaction_feed

   مطلوبقراءةدفعة

   The stream of transactions from banking and card sources.

   شكل البيانات

   Per-transaction: date, amount, direction (debit/credit), description, counterparty if available, balance after.
   يُملأ عادةً بواسطة

   • bank feed integration to the accounting system
   • card processor feed
   • direct bank API connection
   • scheduled CSV import from online banking
2. open_item_register

   مطلوبقراءةطلب

   Receivables, payables, and other open items the bank transactions might match against.

   شكل البيانات

   Open invoices with amount, customer, expected payment date; open bills with amount, supplier, expected payment date; expected receipts from any other source.
   يُملأ عادةً بواسطة

   • accounts receivable and accounts payable modules of the accounting system
   • open items ledger
   • expected receipts log maintained by treasury
3. categorization_history

   مطلوبقراءةمجموعة

   The firm's historical bookkeeping decisions, which the pattern learns from. Without this, categorization is generic and often wrong.

   شكل البيانات

   Historical transactions with their final categorization: GL account, project, class, any custom dimensions.
   يُملأ عادةً بواسطة

   • complete transaction history in the bookkeeping system
   • general ledger with descriptions and categorizations
   • imported historical books from prior accounting platform
4. chart_of_accounts

   مطلوبقراءةطلب

   The valid set of accounts the pattern can categorize into, with definitions.

   شكل البيانات

   Per-account: code, name, type, description, parent account, active or inactive.
   يُملأ عادةً بواسطة

   • chart of accounts in the bookkeeping system
   • structured account master maintained by the finance team
5. bookkeeping_write_destination

   مطلوبكتابةحدث

   Where matched and categorized transactions get recorded.

   شكل البيانات

   Categorized transactions written as journal entries or applied against open items, with reference back to the source bank transaction.
   يُملأ عادةً بواسطة

   • bookkeeping system with API write access
   • queue of approved entries the bookkeeper posts
   • structured journal staged for bookkeeper review
6. ambiguity_review_queue

   مطلوبقراءة + كتابةدفعة

   Where genuinely uncertain transactions go for human decision.

   شكل البيانات

   Transaction with proposed categorization(s), confidence per option, evidence, decision capture.
   يُملأ عادةً بواسطة

   • review queue inside the accounting system
   • weekly review session with the bookkeeper
   • dedicated review UI built for the engagement
7. rule_definition_layer

   موصى بهقراءةمجموعة

   Explicit rules the pattern must always follow that override learned patterns: 'transactions over $X always need approval', 'transactions to vendor Y always go to project Z'.

   شكل البيانات

   Rules with conditions and required actions or constraints.
   إذا مفقود

   Pattern relies entirely on learned patterns. Most firms have hard rules that should be encoded explicitly.
   يُملأ عادةً بواسطة

   • rules table maintained by the finance team
   • small admin UI for rule authoring
   • documented finance policies captured in build phase