NPO-Accounting/import2ledger
7
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
import2ledger/tests/data/imports.yml

1057 lines
30 KiB
YAML
Raw Normal View History

import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
- source: PatreonPatronReport_2017-09-01.csv
patreon: New importer for new patron report CSV format.
2020-08-30 18:21:59 -04:00
importer: patreon.Income2017Importer
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
expect:
- payee: Alex Jones
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
# PyYAML 6 appears to require UnsafeLoader to handle complex Python tags.
date: !date "2017-09-01"
amount: !decimal "1500.00"
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
currency: USD
patreon: Income2017Importer grabs email address.
2021-03-18 11:44:24 -04:00
email: alex@example.org
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
- payee: Dakota Doe
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-09-01"
amount: !decimal "12.00"
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
currency: USD
patreon: Income2017Importer grabs email address.
2021-03-18 11:44:24 -04:00
email: ddoe@example.org
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
patreon: New importer for new patron report CSV format.
2020-08-30 18:21:59 -04:00
- source: PatreonPatronReport_2020-08-01.csv
patreon: Update importer for recent patron changes. RT#12747 All they did was change a couple of column names.
2020-10-05 13:49:39 -04:00
importer: patreon.Income2020AugustImporter
expect:
- payee: Alex Jones
email: ajones@example.com
tier: Even tier
patreon_id: "1234567"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2020-08-01"
amount: !decimal "2"
patreon: Update importer for recent patron changes. RT#12747 All they did was change a couple of column names.
2020-10-05 13:49:39 -04:00
currency: USD
- payee: Breonna
email: breonna@example.org
tier: Odd tier
patreon_id: "234567"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2020-08-02"
amount: !decimal "5.00"
patreon: Update importer for recent patron changes. RT#12747 All they did was change a couple of column names.
2020-10-05 13:49:39 -04:00
currency: USD
- source: PatreonPatronReport_2020-10-01.csv
patreon: Update importer for this month's change. Literally all they did was change the title of the amount column (maybe it doesn't assume USD anymore?).
2020-11-09 16:59:24 -05:00
importer: patreon.Income2020OctoberImporter
expect:
- payee: Alex Jones
email: ajones@example.com
tier: Even tier
patreon_id: "1234567"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2020-08-01"
amount: !decimal "2"
patreon: Update importer for this month's change. Literally all they did was change the title of the amount column (maybe it doesn't assume USD anymore?).
2020-11-09 16:59:24 -05:00
currency: USD
- payee: Breonna
email: breonna@example.org
tier: Odd tier
patreon_id: "234567"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2020-08-02"
amount: !decimal "5.00"
patreon: Update importer for this month's change. Literally all they did was change the title of the amount column (maybe it doesn't assume USD anymore?).
2020-11-09 16:59:24 -05:00
currency: USD
- source: PatreonPatronReport_2020-11-01.csv
patreon: New importer for new patron report CSV format.
2020-08-30 18:21:59 -04:00
importer: patreon.IncomeImporter
expect:
- payee: Alex Jones
email: ajones@example.com
tier: Even tier
patreon_id: "1234567"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2020-08-01"
amount: !decimal "2"
patreon: New importer for new patron report CSV format.
2020-08-30 18:21:59 -04:00
currency: USD
- payee: Breonna
email: breonna@example.org
tier: Odd tier
patreon_id: "234567"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2020-08-02"
amount: !decimal "5.00"
patreon: New importer for new patron report CSV format.
2020-08-30 18:21:59 -04:00
currency: USD
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
- source: PatreonEarnings.csv
hooks.ledger_entry: Look up templates dynamically. If there's a 'ledger entry' key in the entry data, use that value as the name of the template to load. Thanks to this, nbpy2017 could collapse multiple importers into one. Otherwise, build a default template name based on the importer source, and try to use that. All the configuration names now end with "ledger entry" instead of starting with "template". This makes it clearer what they're for, in case we support other kinds of output templates in the future. I ended up changing the names of some of the importers so the default template name was nice, rather than specifying template names for all of them, to reduce the amount of name discrepancies across the codebase.
2017-12-31 18:52:30 -05:00
importer: patreon.ServiceFeesImporter
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
expect:
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-09-01"
amount: !decimal "61.73"
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
currency: USD
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-10-01"
amount: !decimal "117.03"
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
currency: USD
patreon: New importer for revamped earnings report.
2020-12-08 11:31:40 -05:00
- source: PatreonEarnings2020.csv
importer: patreon.EarningsImporter
expect:
- payee: Frances Jones
email: fjones@example.com
user_id: "32101234"
event_id: "30123456"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2020-12-03"
currency: USD
amount: !decimal "5"
tax_amount: !decimal "1"
net_amount: !decimal "4.31"
platform_fee: !decimal "0.25"
processing_fee: !decimal "0.44"
currency_fee: !decimal "0"
patreon: New importer for revamped earnings report.
2020-12-08 11:31:40 -05:00
- payee: Barbara Johnson
email: bjohnson@example.com
user_id: "2345678"
event_id: "34567890"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2020-12-02"
currency: USD
amount: !decimal "6.06"
tax_amount: !decimal "1.27"
net_amount: !decimal "5.14"
platform_fee: !decimal "0.31"
processing_fee: !decimal "0.42"
currency_fee: !decimal "0.19"
patreon: New importer for revamped earnings report.
2020-12-08 11:31:40 -05:00
- payee: Alex Jones
email: ajones@example.com
user_id: "7654321"
event_id: "456789090"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2020-12-01"
currency: USD
amount: !decimal "14"
tax_amount: !decimal "0"
net_amount: !decimal "12.64"
platform_fee: !decimal ".7"
processing_fee: !decimal ".66"
currency_fee: !decimal "0"
patreon: New importer for revamped earnings report.
2020-12-08 11:31:40 -05:00
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
- source: PatreonEarnings.csv
hooks.ledger_entry: Look up templates dynamically. If there's a 'ledger entry' key in the entry data, use that value as the name of the template to load. Thanks to this, nbpy2017 could collapse multiple importers into one. Otherwise, build a default template name based on the importer source, and try to use that. All the configuration names now end with "ledger entry" instead of starting with "template". This makes it clearer what they're for, in case we support other kinds of output templates in the future. I ended up changing the names of some of the importers so the default template name was nice, rather than specifying template names for all of them, to reduce the amount of name discrepancies across the codebase.
2017-12-31 18:52:30 -05:00
importer: patreon.CardFeesImporter
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
expect:
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-09-01"
amount: !decimal "52.47"
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
currency: USD
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-10-01"
amount: !decimal "99.47"
import2ledger: First version. This is a pretty feature-complete version 1. I don't know why I waited this long to commit anything.
2017-10-22 13:38:53 -04:00
currency: USD
patreon: Import VAT withholdings.
2017-10-26 12:40:28 -04:00
- source: PatreonVat.csv
importer: patreon.VATImporter
expect:
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-09-01"
amount: !decimal "2.00"
patreon: Import VAT withholdings.
2017-10-26 12:40:28 -04:00
currency: USD
country_code: AT
country_name: Austria
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-09-01"
amount: !decimal "3.30"
patreon: Import VAT withholdings.
2017-10-26 12:40:28 -04:00
currency: USD
country_code: BE
country_name: Belgium
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-10-01"
amount: !decimal "0.40"
patreon: Import VAT withholdings.
2017-10-26 12:40:28 -04:00
currency: USD
country_code: BG
country_name: Bulgaria
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-10-01"
amount: !decimal "6.05"
patreon: Import VAT withholdings.
2017-10-26 12:40:28 -04:00
currency: USD
country_code: CZ
country_name: Czech Republic
importers: Add an importer for Stripe payments.
2017-11-09 15:06:02 -05:00
patreon: New importer for payouts.
2018-07-10 11:36:07 -04:00
- source: PatreonPayouts.csv
importer: patreon.PayoutImporter
expect:
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2018-04-01"
amount: !decimal "123.45"
pledges_amount: !decimal "0"
transfer_amount: !decimal "123.45"
patreon: New importer for payouts.
2018-07-10 11:36:07 -04:00
currency: USD
- payee: Patreon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2018-05-01"
amount: !decimal "2345.67"
pledges_amount: !decimal "0"
transfer_amount: !decimal "2345.67"
patreon: New importer for payouts.
2018-07-10 11:36:07 -04:00
currency: USD
importers: Add an importer for Stripe payments.
2017-11-09 15:06:02 -05:00
- source: StripePayments.csv
importer: stripe.PaymentImporter
expect:
- payee: Dakota Smith
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-11-08"
amount: !decimal "100.00"
fee: !decimal "3"
tax: !decimal "0"
importers: Add an importer for Stripe payments.
2017-11-09 15:06:02 -05:00
currency: USD
payment_id: ch_oxuish6phae2Raighooghi3U
stripe: Extract more columns from payment data.
2018-01-25 12:11:58 -05:00
customer_id: cus_DohSheeQu8eng3
customer_email: one@example.org
payout_id: po_aeYees2ahtier8ohju7Eeyie
importers: Add an importer for Stripe payments.
2017-11-09 15:06:02 -05:00
description: "Payment for invoice #102"
- payee: Dakota Jones
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-10-28"
amount: !decimal "50.00"
fee: !decimal "1.4"
tax: !decimal "0"
importers: Add an importer for Stripe payments.
2017-11-09 15:06:02 -05:00
currency: USD
payment_id: ch_hHee9ef1aeyee1ruo7ochee9
stripe: Extract more columns from payment data.
2018-01-25 12:11:58 -05:00
customer_id: cus_iepae2Iecae8Ei
customer_email: two@example.org
payout_id: po_aeYees2ahtier8ohju7Eeyie
importers: Add an importer for Stripe payments.
2017-11-09 15:06:02 -05:00
description: "Payment for invoice #100"
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
stripe: Add payouts importer.
2018-01-25 17:59:19 -05:00
- source: StripePayouts.csv
importer: stripe.PayoutImporter
expect:
- payee: Stripe
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-11-30"
amount: !decimal "-50"
currency: USD
payment_count: !decimal "0"
payment_gross: !decimal "0"
payment_fees: !decimal "0"
payment_net: !decimal "0"
refund_count: !decimal "1"
refund_gross: !decimal "-50"
refund_fees: !decimal "0"
refund_net: !decimal "-50"
collected_fee_count: !decimal "0"
collected_fee_gross: !decimal "0"
collected_fee_refund_count: !decimal "0"
collected_fee_refund_gross: !decimal "0"
adjustment_count: !decimal "0"
adjustment_gross: !decimal "0"
adjustment_fees: !decimal "0"
adjustment_net: !decimal "0"
validation_count: !decimal "0"
validation_fees: !decimal "0"
retried_payout_count: !decimal "0"
retried_payout_net: !decimal "0"
total_count: !decimal "1"
total_gross: !decimal "-50"
total_fees: !decimal "0"
total_net: !decimal "-50"
stripe: Add payouts importer.
2018-01-25 17:59:19 -05:00
payout_id: po_faegh6aeghishuethuoSoT2i
destination_id: ba_chu0Woop5queewi2Ea1Aibah
balance_txid: txn_EiKahrazei3aeMohk7EeDigh
failure_txid: ""
- payee: Stripe
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-11-29"
amount: !decimal "146.50"
currency: USD
payment_count: !decimal "2"
payment_gross: !decimal "150"
payment_fees: !decimal "3.5"
payment_net: !decimal "146.5"
refund_count: !decimal "0"
refund_gross: !decimal "0"
refund_fees: !decimal "0"
refund_net: !decimal "0"
collected_fee_count: !decimal "0"
collected_fee_gross: !decimal "0"
collected_fee_refund_count: !decimal "0"
collected_fee_refund_gross: !decimal "0"
adjustment_count: !decimal "0"
adjustment_gross: !decimal "0"
adjustment_fees: !decimal "0"
adjustment_net: !decimal "0"
validation_count: !decimal "0"
validation_fees: !decimal "0"
retried_payout_count: !decimal "0"
retried_payout_net: !decimal "0"
total_count: !decimal "2"
total_gross: !decimal "150"
total_fees: !decimal "3.5"
total_net: !decimal "146.5"
stripe: Add payouts importer.
2018-01-25 17:59:19 -05:00
payout_id: po_Do9pathoo9Pu8jaePhahJa0e
destination_id: ba_chu0Woop5queewi2Ea1Aibah
balance_txid: txn_ahsaixiene6Thie1aiti3tuo
failure_txid: ""
importers.nbpy2017: Yield entries for the original invoice. This lets us write up a cleaner separation between the original act of invoicing and the Stripe payment.
2017-12-18 10:47:04 -05:00
- source: nbpy2017a.html
hooks.ledger_entry: Look up templates dynamically. If there's a 'ledger entry' key in the entry data, use that value as the name of the template to load. Thanks to this, nbpy2017 could collapse multiple importers into one. Otherwise, build a default template name based on the importer source, and try to use that. All the configuration names now end with "ledger entry" instead of starting with "template". This makes it clearer what they're for, in case we support other kinds of output templates in the future. I ended up changing the names of some of the importers so the default template name was nice, rather than specifying template names for all of them, to reduce the amount of name discrepancies across the codebase.
2017-12-31 18:52:30 -05:00
importer: nbpy2017.InvoiceImporter
importers.nbpy2017: Yield entries for the original invoice. This lets us write up a cleaner separation between the original act of invoicing and the Stripe payment.
2017-12-18 10:47:04 -05:00
expect:
- payee: Python Person A
nbpy2017: Bugfix entry data key name for custom Ledger template.
2018-01-24 18:01:16 -05:00
ledger template: nbpy2017 invoice ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-10-19"
amount: !decimal "80.00"
tickets_sold: !decimal "1"
ticket_price: !decimal "80.00"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
ticket_rate: Early Bird (Ticket - Individual Supporter)
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
shirts_sold: !decimal "1"
shirt_price: !decimal "0"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
shirt_rate: "Complimentary for ticket holder (Supporter-level and above) (T-Shirt - Men's/Straight Cut Size L)"
importers.nbpy2017: Yield entries for the original invoice. This lets us write up a cleaner separation between the original act of invoicing and the Stripe payment.
2017-12-18 10:47:04 -05:00
currency: USD
status: Invoice
invoice_id: "83"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
invoice_date: !date "2017-10-19"
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
- payee: Python Person A
nbpy2017: Bugfix entry data key name for custom Ledger template.
2018-01-24 18:01:16 -05:00
ledger template: nbpy2017 payment ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-10-19"
amount: !decimal "80.00"
tickets_sold: !decimal "1"
ticket_price: !decimal "80.00"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
ticket_rate: Early Bird (Ticket - Individual Supporter)
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
shirts_sold: !decimal "1"
shirt_price: !decimal "0"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
shirt_rate: "Complimentary for ticket holder (Supporter-level and above) (T-Shirt - Men's/Straight Cut Size L)"
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
currency: USD
importers.nbpy2017: Yield entries for the original invoice. This lets us write up a cleaner separation between the original act of invoicing and the Stripe payment.
2017-12-18 10:47:04 -05:00
status: Payment
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
invoice_id: "83"
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
invoice_date: !date "2017-10-19"
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
payment_id: ch_ahr0ue8lai1ohqu4Gei4Biem
stripe_id: ch_ahr0ue8lai1ohqu4Gei4Biem
- source: nbpy2017b.html
hooks.ledger_entry: Look up templates dynamically. If there's a 'ledger entry' key in the entry data, use that value as the name of the template to load. Thanks to this, nbpy2017 could collapse multiple importers into one. Otherwise, build a default template name based on the importer source, and try to use that. All the configuration names now end with "ledger entry" instead of starting with "template". This makes it clearer what they're for, in case we support other kinds of output templates in the future. I ended up changing the names of some of the importers so the default template name was nice, rather than specifying template names for all of them, to reduce the amount of name discrepancies across the codebase.
2017-12-31 18:52:30 -05:00
importer: nbpy2017.InvoiceImporter
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
expect:
- payee: Python Person B
nbpy2017: Bugfix entry data key name for custom Ledger template.
2018-01-24 18:01:16 -05:00
ledger template: nbpy2017 invoice ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-12-03"
amount: !decimal "50.00"
tickets_sold: !decimal "1"
ticket_price: !decimal "50.00"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
ticket_rate: Ticket - Unaffiliated Individual
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
shirts_sold: !decimal "0"
shirt_price: !decimal "0"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
shirt_rate: ""
hooks.ledger_entry: Look up templates dynamically. If there's a 'ledger entry' key in the entry data, use that value as the name of the template to load. Thanks to this, nbpy2017 could collapse multiple importers into one. Otherwise, build a default template name based on the importer source, and try to use that. All the configuration names now end with "ledger entry" instead of starting with "template". This makes it clearer what they're for, in case we support other kinds of output templates in the future. I ended up changing the names of some of the importers so the default template name was nice, rather than specifying template names for all of them, to reduce the amount of name discrepancies across the codebase.
2017-12-31 18:52:30 -05:00
status: Invoice
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
invoice_date: !date "2017-12-03"
hooks.ledger_entry: Look up templates dynamically. If there's a 'ledger entry' key in the entry data, use that value as the name of the template to load. Thanks to this, nbpy2017 could collapse multiple importers into one. Otherwise, build a default template name based on the importer source, and try to use that. All the configuration names now end with "ledger entry" instead of starting with "template". This makes it clearer what they're for, in case we support other kinds of output templates in the future. I ended up changing the names of some of the importers so the default template name was nice, rather than specifying template names for all of them, to reduce the amount of name discrepancies across the codebase.
2017-12-31 18:52:30 -05:00
invoice_id: "304"
- payee: Python Person B
nbpy2017: Bugfix entry data key name for custom Ledger template.
2018-01-24 18:01:16 -05:00
ledger template: nbpy2017 payment ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-12-03"
amount: !decimal "50.00"
tickets_sold: !decimal "1"
ticket_price: !decimal "50.00"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
ticket_rate: Ticket - Unaffiliated Individual
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
shirts_sold: !decimal "0"
shirt_price: !decimal "0"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
shirt_rate: ""
importers.nbpy2017: Yield entries for the original invoice. This lets us write up a cleaner separation between the original act of invoicing and the Stripe payment.
2017-12-18 10:47:04 -05:00
status: Payment
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
invoice_date: !date "2017-12-03"
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
payment_id: ch_eishei9aiY8aiqu4lieYiu9i
stripe_id: ch_eishei9aiY8aiqu4lieYiu9i
invoice_id: "304"
- source: nbpy2017c.html
hooks.ledger_entry: Look up templates dynamically. If there's a 'ledger entry' key in the entry data, use that value as the name of the template to load. Thanks to this, nbpy2017 could collapse multiple importers into one. Otherwise, build a default template name based on the importer source, and try to use that. All the configuration names now end with "ledger entry" instead of starting with "template". This makes it clearer what they're for, in case we support other kinds of output templates in the future. I ended up changing the names of some of the importers so the default template name was nice, rather than specifying template names for all of them, to reduce the amount of name discrepancies across the codebase.
2017-12-31 18:52:30 -05:00
importer: nbpy2017.InvoiceImporter
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
expect:
- payee: Python Person C
nbpy2017: Bugfix entry data key name for custom Ledger template.
2018-01-24 18:01:16 -05:00
ledger template: nbpy2017 invoice ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-09-05"
amount: !decimal "60.00"
tickets_sold: !decimal "0"
ticket_price: !decimal "0"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
ticket_rate: Ticket - Talk Proposer
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
shirts_sold: !decimal "2"
shirt_price: !decimal "30.00"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
shirt_rate: "T-Shirt - Men's/Straight Cut Size M"
hooks.ledger_entry: Look up templates dynamically. If there's a 'ledger entry' key in the entry data, use that value as the name of the template to load. Thanks to this, nbpy2017 could collapse multiple importers into one. Otherwise, build a default template name based on the importer source, and try to use that. All the configuration names now end with "ledger entry" instead of starting with "template". This makes it clearer what they're for, in case we support other kinds of output templates in the future. I ended up changing the names of some of the importers so the default template name was nice, rather than specifying template names for all of them, to reduce the amount of name discrepancies across the codebase.
2017-12-31 18:52:30 -05:00
status: Invoice
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
invoice_date: !date "2017-09-05"
hooks.ledger_entry: Look up templates dynamically. If there's a 'ledger entry' key in the entry data, use that value as the name of the template to load. Thanks to this, nbpy2017 could collapse multiple importers into one. Otherwise, build a default template name based on the importer source, and try to use that. All the configuration names now end with "ledger entry" instead of starting with "template". This makes it clearer what they're for, in case we support other kinds of output templates in the future. I ended up changing the names of some of the importers so the default template name was nice, rather than specifying template names for all of them, to reduce the amount of name discrepancies across the codebase.
2017-12-31 18:52:30 -05:00
invoice_id: "11"
- payee: Python Person C
nbpy2017: Bugfix entry data key name for custom Ledger template.
2018-01-24 18:01:16 -05:00
ledger template: nbpy2017 payment ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-09-05"
amount: !decimal "60.00"
tickets_sold: !decimal "0"
ticket_price: !decimal "0"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
ticket_rate: Ticket - Talk Proposer
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
shirts_sold: !decimal "2"
shirt_price: !decimal "30.00"
nbpy2017: Report item rate names and final unit prices. This keeps more of the RBI calculation in the templates, where it belongs. Template logic has become more capable since this importer was first written, which makes this change practical.
2019-10-15 15:41:47 -04:00
shirt_rate: "T-Shirt - Men's/Straight Cut Size M"
importers.nbpy2017: Yield entries for the original invoice. This lets us write up a cleaner separation between the original act of invoicing and the Stripe payment.
2017-12-18 10:47:04 -05:00
status: Payment
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
invoice_date: !date "2017-09-05"
importers: New importer for North Bay Python invoices. This probably has no use outside Conservancy.
2017-12-17 20:46:00 -05:00
payment_id: ch_daer0ahwoh9oDeiqu2eimoD7
stripe_id: ch_daer0ahwoh9oDeiqu2eimoD7
invoice_id: "11"
tests: Test Amazon Affiliate Earnings importer from 25c6454.
2017-12-30 16:14:15 -05:00
- source: AmazonAffiliateEarnings.csv
importer: amazon.EarningsImporter
csv: Support importing squared CSV spreadsheets. See the test comment for more rationale.
2019-08-28 10:22:10 -04:00
header_rows: 1
header_cols: 12
tests: Test Amazon Affiliate Earnings importer from 25c6454.
2017-12-30 16:14:15 -05:00
expect:
- payee: Amazon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2016-12-20"
amount: !decimal "4.24"
tests: Test Amazon Affiliate Earnings importer from 25c6454.
2017-12-30 16:14:15 -05:00
currency: USD
- payee: Amazon
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
date: !date "2017-01-07"
amount: !decimal "-.08"
tests: Test Amazon Affiliate Earnings importer from 25c6454.
2017-12-30 16:14:15 -05:00
currency: USD
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
benevity: Version the current importer. The report format has changed slightly in 2019.
2019-02-15 11:47:27 -05:00
- source: Benevity2018.csv
importer: benevity.Donations2018Importer
csv: Support importing squared CSV spreadsheets. See the test comment for more rationale.
2019-08-28 10:22:10 -04:00
header_rows: 11
header_cols: 17
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-28"
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal 20
donation_amount: !decimal 20
match_amount: !decimal 0
match_amount: !decimal 0
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
payee: Dakota Smith
corporation: Company A
project: ""
comment: ""
frequency: One-time
transaction_id: 67890QWERT
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-30"
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 25
net_amount: !decimal 25
donation_amount: !decimal 25
match_amount: !decimal 0
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
payee: Dakota Smith
corporation: Company A
project: ""
comment: ""
frequency: One-time
transaction_id: 67890WERTY
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-19"
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 10
net_amount: !decimal 10
donation_amount: !decimal 0
match_amount: !decimal 10
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
payee: Anonymous
corporation: Company B
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890ERTYU
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-19"
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal 20
donation_amount: !decimal 0
match_amount: !decimal 20
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
payee: Anonymous
corporation: Company B
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890RTYUI
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-19"
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 30
net_amount: !decimal 30
donation_amount: !decimal 30
match_amount: !decimal 0
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
payee: Anonymous
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
corporation: Company B
project: ""
comment: ""
frequency: Recurring
transaction_id: 67890TYUIO
ledger template: benevity donations ledger entry
- source: Benevity2019.csv
importer: benevity.Donations2019Importer
csv: Support importing squared CSV spreadsheets. See the test comment for more rationale.
2019-08-28 10:22:10 -04:00
header_rows: 11
header_cols: 21
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-28"
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal 20
donation_amount: !decimal 20
match_amount: !decimal 0
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
payee: Dakota Smith
corporation: Company A
project: ""
comment: ""
frequency: One-time
transaction_id: 67890QWERT
benevity: Version the current importer. The report format has changed slightly in 2019.
2019-02-15 11:47:27 -05:00
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-30"
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 25
net_amount: !decimal 25
donation_amount: !decimal 25
match_amount: !decimal 0
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
payee: Dakota Smith
corporation: Company A
project: ""
comment: ""
frequency: One-time
transaction_id: 67890WERTY
benevity: Version the current importer. The report format has changed slightly in 2019.
2019-02-15 11:47:27 -05:00
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-19"
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 10
net_amount: !decimal 10
donation_amount: !decimal 0
match_amount: !decimal 10
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
payee: Anonymous
corporation: Company B
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890ERTYU
benevity: Version the current importer. The report format has changed slightly in 2019.
2019-02-15 11:47:27 -05:00
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-19"
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal 20
donation_amount: !decimal 0
match_amount: !decimal 20
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
payee: Anonymous
corporation: Company B
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890RTYUI
benevity: Version the current importer. The report format has changed slightly in 2019.
2019-02-15 11:47:27 -05:00
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-19"
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 30
net_amount: !decimal 30
donation_amount: !decimal 30
match_amount: !decimal 0
donation_fee: !decimal 0
match_fee: !decimal 0
merchant_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
tests: Test Benevity disbursement importer from 1b1e2d0.
2017-12-30 16:39:38 -05:00
payee: Anonymous
corporation: Company B
project: ""
comment: ""
frequency: Recurring
transaction_id: 67890TYUIO
benevity: Version the current importer. The report format has changed slightly in 2019.
2019-02-15 11:47:27 -05:00
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-18"
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal "19.55"
donation_amount: !decimal 10
match_amount: !decimal 10
donation_fee: !decimal ".1"
match_fee: !decimal ".2"
merchant_fee: !decimal ".15"
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
payee: Anonymous
corporation: Company C
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890YUIOP
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-21"
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal "19.55"
donation_amount: !decimal 10
match_amount: !decimal 10
donation_fee: !decimal ".1"
match_fee: !decimal ".2"
merchant_fee: !decimal ".15"
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: null
payee: Anonymous
corporation: Company C
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890ASDFG
ledger template: benevity donations ledger entry
- source: Benevity2020.csv
importer: benevity.Donations2020Importer
header_rows: 11
header_cols: 23
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2019-10-28"
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal 20
donation_amount: !decimal 20
match_amount: !decimal 0
donation_fee: !decimal 0
merchant_fee: !decimal 0
match_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: ""
payee: Dakota Smith
corporation: Company A
project: ""
comment: ""
frequency: One-time
transaction_id: 67890QWERT
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2019-10-30"
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 25
net_amount: !decimal 25
donation_amount: !decimal 25
match_amount: !decimal 0
donation_fee: !decimal 0
merchant_fee: !decimal 0
match_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: ""
payee: Dakota Smith
corporation: Company A
project: ""
comment: ""
frequency: One-time
transaction_id: 67890WERTY
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2019-10-19"
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 10
net_amount: !decimal 10
donation_amount: !decimal 0
match_amount: !decimal 10
donation_fee: !decimal 0
merchant_fee: !decimal 0
match_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: ""
payee: Anonymous
corporation: Company B
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890ERTYU
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2019-10-19"
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal 20
donation_amount: !decimal 0
match_amount: !decimal 20
donation_fee: !decimal 0
merchant_fee: !decimal 0
match_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: ""
payee: Anonymous
corporation: Company B
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890RTYUI
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2019-10-19"
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 30
net_amount: !decimal 30
donation_amount: !decimal 30
match_amount: !decimal 0
donation_fee: !decimal 0
merchant_fee: !decimal 0
match_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: ""
payee: Anonymous
corporation: Company B
project: ""
comment: ""
frequency: Recurring
transaction_id: 67890TYUIO
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2019-10-18"
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal "19.55"
donation_amount: !decimal 10
match_amount: !decimal 10
donation_fee: !decimal ".3"
merchant_fee: !decimal ".15"
match_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: ""
payee: Anonymous
corporation: Company C
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890YUIOP
ledger template: benevity donations ledger entry
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2019-10-21"
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
currency: USD
disbursement_id: ABCDE12345
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 20
net_amount: !decimal "19.55"
donation_amount: !decimal 10
match_amount: !decimal 10
donation_fee: !decimal ".3"
merchant_fee: !decimal ".15"
match_fee: !decimal 0
benevity: Add support for latest Benevity format.
2019-12-30 15:45:14 -05:00
fee_comment: ""
benevity: Support new 2019 report format.
2019-02-15 12:49:57 -05:00
payee: Anonymous
corporation: Company C
project: ""
comment: ""
frequency: Unknown
transaction_id: 67890ASDFG
ledger template: benevity donations ledger entry
brightfunds: New importer. This commit adds infrastructure to treat XLS files like CSV files, and import them using the base classes that already exist for that.
2018-01-21 17:04:37 -05:00
- source: BrightFunds.xls
brightfunds: Add importer for new CSV format.
2020-11-09 16:40:33 -05:00
importer: brightfunds.DonorReportXLSImporter
brightfunds: New importer. This commit adds infrastructure to treat XLS files like CSV files, and import them using the base classes that already exist for that.
2018-01-21 17:04:37 -05:00
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-10-20"
brightfunds: New importer. This commit adds infrastructure to treat XLS files like CSV files, and import them using the base classes that already exist for that.
2018-01-21 17:04:37 -05:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 120
brightfunds: New importer. This commit adds infrastructure to treat XLS files like CSV files, and import them using the base classes that already exist for that.
2018-01-21 17:04:37 -05:00
payee: Dakota Smith
corporation: Company
company_name: ""
designation: ""
donor_name: Company
donor_email: ""
fund: ""
on_behalf_of: Dakota Smith
type: Matched Donation
oreilly: New importer.
2018-07-03 10:24:21 -04:00
brightfunds: Add importer for new CSV format.
2020-11-09 16:40:33 -05:00
- source: BrightFunds.csv
importer: brightfunds.DonorReportImporter
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2020-10-01"
brightfunds: Add importer for new CSV format.
2020-11-09 16:40:33 -05:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 15
brightfunds: Add importer for new CSV format.
2020-11-09 16:40:33 -05:00
payee: Company
corporation: Company
company_name: Company
designation: ""
donor_name: Company
donor_email: ""
fund: ""
on_behalf_of: Employed Person
type: MatchingTransaction
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2020-09-24"
brightfunds: Add importer for new CSV format.
2020-11-09 16:40:33 -05:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 15
brightfunds: Add importer for new CSV format.
2020-11-09 16:40:33 -05:00
payee: Employed Person
corporation: Company
company_name: Company
designation: ""
donor_name: Employed Person
donor_email: person@example.com
fund: ""
on_behalf_of: ""
type: CreditCardTransaction
oreilly: New importer.
2018-07-03 10:24:21 -04:00
- source: OReillyRoyalties.csv
importer: oreilly.RoyaltiesImporter
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-03-31"
start_date: !date "2018-03-01"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
paid_date: null
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "11.96"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-02-28"
start_date: !date "2018-02-01"
paid_date: !date "2018-03-29"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "20.83"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-01-31"
start_date: !date "2018-01-01"
paid_date: !date "2018-03-29"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "8.51"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-03-31"
start_date: !date "2017-03-01"
paid_date: !date "2017-04-28"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "26.91"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-01-31"
start_date: !date "2017-01-01"
paid_date: !date "2017-04-28"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "12.33"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2016-12-31"
start_date: !date "2016-12-01"
paid_date: !date "2017-04-28"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "9.15"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2016-09-30"
start_date: !date "2016-09-01"
paid_date: !date "2016-12-16"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "26.19"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2016-08-31"
start_date: !date "2016-08-01"
paid_date: !date "2016-11-30"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "27.58"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2010-03-31"
start_date: !date "2010-01-01"
paid_date: !date "2010-03-31"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "73.85"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
- source: OReillyPayments.csv
importer: oreilly.PaymentsImporter
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-03-29"
paid_date: !date "2018-03-29"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "29.34"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-04-27"
paid_date: !date "2017-04-28"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "26.91"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2017-04-24"
paid_date: !date "2017-04-28"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "21.48"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2016-12-16"
paid_date: !date "2016-12-16"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "26.19"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2016-11-29"
paid_date: !date "2016-11-30"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "27.58"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2010-03-31"
paid_date: !date "2010-03-31"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "73.85"
oreilly: New importer.
2018-07-03 10:24:21 -04:00
payee: "O'Reilly Media, Inc."
yourcause: New importer.
2019-02-25 12:39:19 -05:00
- source: YourCause.csv
importer: yourcause.DonationsImporter
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-12-20"
yourcause: New importer.
2019-02-25 12:39:19 -05:00
currency: USD
original_currency: USD
payment_id: "10006789"
transaction_id: 2-34567891
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 12
original_amount: !decimal 12
received_amount: !decimal 12
donor_amount: !decimal 12
match_amount: !decimal 0
yourcause: New importer.
2019-02-25 12:39:19 -05:00
dedication_type: ""
dedication: ""
designation: Note
payee: Dakota Smith
donor: Dakota Smith
corporation: Company A
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-12-31"
yourcause: New importer.
2019-02-25 12:39:19 -05:00
currency: USD
original_currency: USD
payment_id: "10006789"
transaction_id: 2-34567893
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 14
original_amount: !decimal 14
received_amount: !decimal 14
donor_amount: !decimal 14
match_amount: !decimal 0
yourcause: New importer.
2019-02-25 12:39:19 -05:00
dedication_type: ""
dedication: ""
designation: ""
payee: Anonymous
donor: Anonymous
corporation: Company B
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-12-20"
yourcause: New importer.
2019-02-25 12:39:19 -05:00
currency: USD
original_currency: USD
payment_id: "10006789"
transaction_id: 2-34567895
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 12
original_amount: !decimal 12
received_amount: !decimal 12
donor_amount: !decimal 0
match_amount: !decimal 12
yourcause: New importer.
2019-02-25 12:39:19 -05:00
dedication_type: ""
dedication: ""
designation: Note
payee: Company A
donor: Dakota Smith
corporation: Company A
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-12-31"
yourcause: New importer.
2019-02-25 12:39:19 -05:00
currency: USD
original_currency: USD
payment_id: "10006789"
transaction_id: 2-34567897
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal 14
original_amount: !decimal 14
received_amount: !decimal 14
donor_amount: !decimal 0
match_amount: !decimal 14
yourcause: New importer.
2019-02-25 12:39:19 -05:00
dedication_type: ""
dedication: ""
designation: ""
payee: Company B
donor: Anonymous
corporation: Company B
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-12-15"
yourcause: New importer.
2019-02-25 12:39:19 -05:00
currency: USD
original_currency: GBP
payment_id: "10006789"
transaction_id: 2-34567899
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "12.50"
original_amount: !decimal 10
received_amount: !decimal "12.50"
donor_amount: !decimal "12.50"
match_amount: !decimal 0
yourcause: New importer.
2019-02-25 12:39:19 -05:00
dedication_type: ""
dedication: ""
designation: ""
payee: Alex Jones
donor: Alex Jones
corporation: Company C
importers: New importer eventbrite.
2019-07-04 19:10:11 -04:00
- source: EventBrite.csv
importer: eventbrite.SalesImporter
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2018-11-27"
importers: New importer eventbrite.
2019-07-04 19:10:11 -04:00
currency: USD
event_name: First Event
event_id: "12345678901"
order_id: "123432101"
attendee_id: "432123401"
payee: Alex Jones
corporation: ""
ticket_type: Discount Ticket
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
quantity: !decimal "1"
amount: !decimal "10"
total_fees: !decimal "3.99"
eventbrite_fees: !decimal "2.99"
payment_fees: !decimal "1"
tax: !decimal 0
- date: !date "2018-12-06"
importers: New importer eventbrite.
2019-07-04 19:10:11 -04:00
currency: USD
event_name: First Event
event_id: "12345678901"
order_id: "123432102"
attendee_id: "432123402"
payee: Bret Baker
corporation: ""
ticket_type: Regular Ticket
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
quantity: !decimal "1"
amount: !decimal "30"
total_fees: !decimal "3.99"
eventbrite_fees: !decimal "2.99"
payment_fees: !decimal "1"
tax: !decimal 0
- date: !date "2019-01-07"
importers: New importer eventbrite.
2019-07-04 19:10:11 -04:00
currency: USD
event_name: First Event
event_id: "12345678901"
order_id: "123432103"
attendee_id: "432123403"
payee: Cam Smith
corporation: SampleCo
ticket_type: Premium Ticket
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
quantity: !decimal "1"
amount: !decimal "60"
total_fees: !decimal "6.39"
eventbrite_fees: !decimal "4.39"
payment_fees: !decimal "2"
tax: !decimal 0
- date: !date "2019-01-23"
eventbrite: Sales report can include currency. It's a selectable column that I apparently failed to include in my last report. Keep USD around as a default for convenience.
2019-07-29 11:41:49 -04:00
currency: EUR
importers: New importer eventbrite.
2019-07-04 19:10:11 -04:00
event_name: Second Event
event_id: "12345678902"
order_id: "123432110"
attendee_id: "432123410"
payee: Jam Jones
corporation: ""
ticket_type: Discount Ticket
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
quantity: !decimal "1"
amount: !decimal "25"
total_fees: !decimal "3.99"
eventbrite_fees: !decimal "2.99"
payment_fees: !decimal "1"
tax: !decimal 0
github: New importer.
2020-07-07 10:16:29 -04:00
- source: GitHubSponsors.csv
importer: github.SponsorsImporter
expect:
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2020-01-02"
github: Update to match fiscal host reporting. In general the fiscal host reporting isn't as nice as the project reporting, so I hope someday we can revert this change, but until then that's what we're using.
2020-10-05 13:40:29 -04:00
payee: exampleA
github: New importer.
2020-07-07 10:16:29 -04:00
handle: exampleA
email: ajones@example.com
transaction_id: ch_1Gabcdefghijklmnopqrstuv
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "1"
github: New importer.
2020-07-07 10:16:29 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2020-01-03"
github: New importer.
2020-07-07 10:16:29 -04:00
payee: exampleB
handle: exampleB
email: ""
transaction_id: 1023ABCD5678EFGHI
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "10"
github: New importer.
2020-07-07 10:16:29 -04:00
currency: USD
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
- date: !date "2020-01-04"
github: Update to match fiscal host reporting. In general the fiscal host reporting isn't as nice as the project reporting, so I hope someday we can revert this change, but until then that's what we're using.
2020-10-05 13:40:29 -04:00
payee: exampleC
github: New importer.
2020-07-07 10:16:29 -04:00
handle: exampleC
email: info@example.com
transaction_id: ch_1Gabcdefghijklmnopqrstuw
Add !date and !decimal YAML constructors to avoid unsafe parsing mode At some point the defaults for pyyaml were switched to safe parsing mode, so that the previous arbitrary Python YAML tags like "!!python/object/apply:datetime.date [2017, 9, 1]" no longer work. A better way is to define our own explicit constructors to avoid unsafe mode.
2025-09-19 17:21:47 +10:00
amount: !decimal "120"
github: New importer.
2020-07-07 10:16:29 -04:00
currency: USD
Reference in a new issue Copy permalink