정규식 거래 파서
은행 거래를 분류하는 정규식 패턴을 구축하세요.
이 도구가 마음에 드시나요? portfolios.tools를 영원히 무료로 유지하는 데 도움을 주세요.
작동 방식
Write a regex pattern with capture groups and paste sample bank transaction descriptions, one per line. The tool tests each line against your pattern. Export CSV from your bank and paste the description column. Strip amount and date columns first. The explanation panel breaks down each regex token so you can learn as you build. Personal finance dashboards often need 30 to 50 patterns covering groceries, dining, transport, and subscriptions. Paste sample brokerage CSV lines and define capture groups for date, symbol, quantity, and amount fields. Test pattern on header row plus first data row before running against full ten thousand line export. Paste sample brokerage CSV lines and define capture groups for date, symbol, quantity, and amount fields. Test pattern on header row plus first data row before running against full ten thousand line export.
Review match results, capture groups, coverage percentage, and category groupings. The explanation panel helps you understand regex components. Iterate patterns until unmatched count is small. Copy working patterns into your personal finance automation scripts or spreadsheet IMPORT formulas for ongoing categorization. Split complex bank formats into merchant and category capture groups for easier maintenance when statements change format. Budget apps like Actual Budget and Firefly III accept import rules similar to patterns tested here. Test regex against twenty lines before importing thousand row files: one bad pattern mislabels entire history. Capture group tester highlights which lines fail match before importing full history. European brokers often use semicolon delimiter: adjust pattern before US comma assumptions. Test regex against twenty lines before importing thousand row files: one bad pattern mislabels entire history. Capture group tester highlights which lines fail match before importing full history. European brokers often use semicolon delimiter: adjust pattern before US comma assumptions.
twenty lines before importing thousand row files: one bad pattern mislabels entire history. Capture group tester highlights which lines fail match before importing full history. European brokers often use semicolon delimiter: adjust pattern before US comma assumptions. Test regex against twenty lines before importing thousand row files: one bad pattern mislabels entire history. Capture group tester highlights which lines fail match before importing full history. European brokers often use semicolon delimiter: adjust pattern before US comma assumptions.
입력값이 변경될 때마다 정규식 거래 파서을(를) 사용하세요: 시장 변동, 새로운 기여금 또는 수정된 개인 가정 후. 소프트웨어 설치 없이 빠른 재실행을 위해 페이지를 북마크하세요.
단계별 안내
- 정규식 거래 파서을(를) 열고 현재 입력값을 입력하세요.
- 계산된 출력과 요약 테이블을 검토하세요.
- 가정을 조정하고 시나리오를 나란히 비교하세요.
실전 예제
Write a regex pattern with capture groups and paste sample bank transaction descriptions, one per line. Enter the sample inputs described in How it works to reproduce the scenario step by step.
한 번에 하나의 입력을 조정하여 민감도를 확인하세요. 정규식 거래 파서은(는) 즉시 업데이트되므로 행동하기 전에 낙관적 및 보수적 가정을 스트레스 테스트할 수 있습니다.
이 계산기를 사용할 때
Reach for Regex Transaction Parser when build regex patterns to categorize bank transactions.. It suits quick what if analysis before trades, allocation changes, or plan updates.
결정이 세금, 유동성 또는 하나의 공식이 포착하는 것 이상의 다년 전망을 포괄할 때 관련 도구와 함께 사용하세요.
흔한 실수
입력 단위나 오래된 시장 가격을 확인하지 않고 출력을 복사하는 것은 정규식 거래 파서에서 흔한 오류입니다. 행동하기 전에 티커, 백분율 및 날짜를 확인하세요.
단일 기준 시나리오만 실행하면 꼬리 위험을 무시합니다. 보수적 입력으로 스트레스 테스트하고 결정이 중요할 때 아래 나열된 관련 도구와 비교하세요.
공식
Regex tested via new RegExp(pattern, 'i'). Matches and captures groups via exec(). Coverage = Matched Count / Total Samples × 100. Category map groups descriptions by capture group index.
Case insensitive matching. Explanation panel decodes common regex tokens for learning. Does not support lookbehind on all browsers. Escape special characters in merchant names like L\&L BAR. Production pipelines should log unmatched transactions weekly for pattern maintenance. Word boundaries \b help avoid partial matches inside longer merchant strings. Parser runs in browser only: never upload statements with account numbers to external servers. ReDoS risk low for simple patterns but avoid catastrophic nested quantifiers on huge files. ISO date YYYY MM DD output format sorts correctly in downstream ledger imports without reparse. Never upload statements with account numbers to external servers: parser runs locally. Parser runs in browser only: never upload statements with account numbers to external servers. ReDoS risk low for simple patterns but avoid catastrophic nested quantifiers on huge files. ISO date YYYY MM DD output format sorts correctly in downstream ledger imports without reparse. Never upload statements with account numbers to external servers: parser runs locally.
제한 사항 및 가정
Case insensitive matching. Explanation panel decodes common regex tokens for learning. Does not support lookbehind on all browsers. Escape special characters in merchant names like L\&L BAR. Production pipelines should log unmatched transactions weekly for pattern maintenance. Word boundaries \b help avoid partial matches inside longer merchant strings. Parser runs in browser only: never upload statements with account numbers to external servers. ReDoS risk low for simple patterns but avoid catastrophic nested quantifiers on huge files. ISO date YYYY MM DD output format sorts correctly in downstream ledger imports without reparse. Never upload statements with account numbers to external servers: parser runs locally. Parser runs in browser only: never upload statements with account numbers to external servers. ReDoS risk low for simple patterns but avoid catastrophic nested quantifiers on huge files. ISO date YYYY MM DD output format sorts correctly in downstream ledger imports without reparse. Never upload statements with account numbers to external servers: parser runs locally. Regex Transaction Parser does not replace personalized advice. Fees, slippage, account specific rules, and behavioral constraints may change real world outcomes.
주요 용어
- How does the regex parser categorize transactions
- Enter a regex pattern and sample transaction descriptions.
- How do capture groups work
- Capture groups are marked by parentheses ().
- 모델 가정
- Coverage = (Matched / Total Samples) × 100.
대안 비교
SQL to TypeScript Generator helps type transaction database schemas for finance apps. Use those calculators when regex transaction parser alone does not capture the full decision.
portfolios.tools의 내부 링크는 계산기 체인을 도와줍니다: 먼저 정규식 거래 파서을(를) 실행한 다음, 아래 관련 섹션의 전문 도구로 엣지 케이스를 검증하세요.
FAQ
How does the regex parser categorize transactions?
Enter a regex pattern and sample transaction descriptions. The tool tests each description against the pattern, extracts capture groups, and categorizes each match by the specified group number. The regex engine uses case insensitive matching by default to catch variations like amazon, Amazon, or AMAZON as the same merchant. Test with 20 to 50 real bank export lines for reliable coverage estimates. Chase, Bank of America, and Wells Fargo exports use different description formats requiring separate pattern libraries. Credit card versus checking descriptions for the same merchant often need distinct patterns. Named groups map to JSON keys in output: use (?<date>...) syntax for readable transformation templates. Multiline CSV with embedded commas inside quotes requires regex that respects quoted field boundaries. Named capture groups map to JSON keys for date symbol quantity and amount fields. Named groups map to JSON keys in output: use (?<date>...) syntax for readable transformation templates. Multiline CSV with embedded commas inside quotes requires regex that respects quoted field boundaries. Named capture groups map to JSON keys for date symbol quantity and amount fields.
How do capture groups work?
Capture groups are marked by parentheses (). Group 1 is typically the category name. Adjust categoryGroup parameter to use a different capture group for categorization. Example pattern (AMAZON|WALMART).*?(Grocery|Shopping) assigns category from group 2. Non capturing groups (?:...) do not count toward group indices. Named groups are not supported; use numeric group index only for category assignment. Test capture group output on five samples before deploying to production categorization scripts. European date formats need explicit day month year pattern: US default MM/DD/YYYY fails on many EU exports. European date formats need explicit day month year pattern: US default MM/DD/YYYY fails on many EU exports.
What does coverage percentage mean?
Coverage = (Matched / Total Samples) × 100. This shows what percentage of your transaction descriptions the regex pattern successfully matches. Aim for 90%+ coverage before importing patterns into budgeting apps like YNAB or Monarch. Unmatched lines reveal merchants needing additional patterns or broader alternation groups. Track coverage monthly as banks add new merchant descriptor formats to statement lines. Multi currency lines require separate regex branch or normalized amount group after currency symbol strip. Split lines on comma versus semicolon based on broker locale export settings. Multi currency lines require separate regex branch or normalized amount group after currency symbol strip. Split lines on comma versus semicolon based on broker locale export settings.
How are categories assigned?
If a sample matches, it is assigned to the category from the specified capture group. If no match, it is marked as Unmatched. The category map groups matched descriptions by category. Review unmatched samples first: they often share prefixes like POS DEBIT or ACH that you can optionally strip in preprocessing. Duplicate merchant names with different suffixes may need separate alternation branches in one pattern.
How do I build good transaction regex?
Start with known patterns like AMAZON or WALMART for merchant matching. Test against real descriptions and iterate until coverage is high. The explanation panel decodes regex tokens. Use alternation (MERCHANT1|MERCHANT2) for category groups. Anchor patterns with ^ when descriptions always start with the merchant name for faster matching. Build a library of patterns per category and combine with logical OR for production import pipelines. Plaid and MX aggregator formats use different description strings than raw bank CSV exports. Save working patterns in localStorage per broker: Schwab, IBKR, and Degiro use different column orders. Export parsed JSON to compare against broker official gain loss report for reconciliation audit. Share working regex patterns with tax preparer when importing multi year broker history into gain loss software. Save working patterns in localStorage per broker: Schwab, IBKR, and Degiro use different column orders. Export parsed JSON to compare against broker official gain loss report for reconciliation audit.
휴대폰이나 태블릿에서 정규식 거래 파서을(를) 사용할 수 있나요?
예. 이 도구는 데스크톱과 동일한 공식으로 모바일 브라우저에서 완전히 실행됩니다. 선택적 localStorage는 브라우저 설정에서 활성화된 경우 기기에 입력값을 기억할 수 있습니다.
정규식 거래 파서을(를) 사용할 때 내 데이터는 어디에 저장되나요?
당사 서버 어디에도 없습니다. 계산은 브라우저에서 로컬로 실행됩니다. 선택적 localStorage는 기기에서만 양식 필드를 저장하며 네트워크를 통해 포트폴리오 번호를 전송하지 않습니다.
세금 또는 법적 결정에 정규식 거래 파서에 의존해야 하나요?
아니요. 이 도구는 교육용 수학만 제공합니다. 세법, 계좌 규칙 및 개인 상황은 다양합니다. 중대한 결과를 초래하는 거래 전에 자격을 갖춘 세무 또는 법률 전문가와 상담하세요.
관련 도구
SQL to TypeScript Generator helps type transaction database schemas for finance apps. API Mock Generator creates sample payloads for testing categorization webhooks. Cron Market Scheduler supports nightly jobs that import and categorize new bank CSV exports. Latte Factor Calculator complements transaction categorization for discretionary spending analysis. Sinking Fund Planner uses category totals from parsed transactions to allocate monthly savings goals. CSV to Financial JSON Converter offers preset broker maps when regex feels heavy for standard exports. CSV to Financial JSON Converter offers preset broker maps when regex feels heavy for standard exports.